Support Board
Date/Time: Wed, 10 Sep 2025 05:13:16 +0000
Post From: Issues with v2712 vs v2700
| [2024-12-02 18:13:20] |
| User719512 - Posts: 321 |
|
Experienced unresponsive and lagging issues with v2712 with chartbooks that worked perfectly on v2700. I see in other threads that you believe this should not be happening, but many others and I are in fact experiencing issues and the only thing that changed was the version of Sierra. A friend sent me a chartbook with such issues and I saw hangs while I translated symbols and data was loading. After a long long wait, the chart did respond, but very slowly. I noticed 3 of his charts had 40, 60 and 60 update times. Q1: How would this impact your new timer models where an existing/old chart with perhaps existing update values that might be too low for the new timer model work when opened for the first time? Q2: This is not new, but something to consider, and something that the Windows message pump also tries to alleviate, is ensuring the UI, menus, etc. remain responsive even if some other parts of the app are not. Observation: Things seem to be a lot worse while data is downloading and refreshing. As a test, click once and hover over the Sierra menus while a chart is loading and move the mouse over the main menu names to see the menus display and change as the mouse is moved. While existent in v2700, the unresponsiveness of these actions seems works in v2712. Q3: related to Q1, can someone get into a spot where if they set the global chart update interval too low, or set individual chart intervals too low that all of Sierra becomes less responsive because some charts are now hogging all the resource and cause some unintended side effects? Same question for opening an older chartbook that has too aggressive update intervals. Will Sierra detect this and/or ensure all charts, and the Sierra UI get cycles and not get starved by other charts? Other: While doing some testing with v2712, I got into some state once where all of Sierra froze and it also caused every other Windows apps to hang, and I could not alt-tab switch to them or bring them to the front with the mouse. This seems to indicate that Sierra was somehow blocking the Windows message pump. Once I terminated Sierra, my system went back to normal. Summary: I cannot explain a reason everything that I experienced, or track down the exact cause, but like others, things that worked last week are not working now. |