Login Page - Create Account

Support Board


Date/Time: Wed, 10 Jun 2026 19:08:49 +0000



Post From: Rendering problems in subinstance

[2026-06-10 17:36:18]
User512353 - Posts: 143
It is the only chartbook in the sub-instance.
There is no chart-DOM or trading-DOM open in the chartbook, no t&s window either.
As far as I can quickly overview this, there are no transparencies in the chartbook, and definitely no CPU-heavy studies like VbP or TPO.
The spreadsheets do heavy calculations, I think about 1000 rows.

However, all this does not explain why the problem only shows up in the sub-instance.

From my observation that the problem disappears when the data stream ends at 16:00 central time, plus the fact that no CPU or GPU stress is observed, (plus my 30+ years professional programming experience :-)), I would conclude that there is a problem somewhere in the concurrent execution of the DTC client and the graphics renderer, where either something is repeatedly stalled waiting on some semaphore or something like that, or the rendering process for some reason is not granted sufficient time slices. But I am no expert on GDI questions. It does not look like a GDI renderer or compositor problem to me, because the GUI is not frozen, e.g. if I click on a scrollbar at the bottom of a chart window, with many seconds delay it will do the scroll, long before the extensive rendering process on the widgets is complete. The problem is somewhere else.

I should have mentioned: The chartbook is charting MNQ, so it is definitely getting massive amounts of data.
And again: The charts itself in all chart regions do update correctly without noticeable delay.
It is just the other "parts" on the main window and child windows that show the massive rendering delays.