SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and now iOS Charting & Android Chart Components
Please use the forums below to ask questions about SciChart. Take a moment to read our Question asking guidelines on how to ask a good question and our support policy. We also have a tag=SciChart on Stackoverflow.com where you can earn rep for your questions!
Please note: SciChart team will only answer questions from customers with active support subscriptions. Expired support questions will be ignored. If your support status shows incorrectly, contact us and we will be glad to help.
We upgraded from version 1.7 of SciChart to 2.3.5129.39011. Since then we are observing application freeze (as explained below) once in a while. 2 days ago we could reproduce it reliably on one of the machine. We observed that freeze does not happen if we remove SciChart. So we are now sure that freeze is caused by SciChart.
The issue is as follows.
When we plot some graph, our application will stop updating the UI. Application is still responsive, i.e. user can still click on the buttons and buttons will respond. But UI will not update at all e.g. button text will not update etc.
On 8 core machine one of the core is running at 100%. Our application takes that entire core i.e. running at 13%. When we see the process dump all that core is used by Main thread.
It is difficult to reproduce. But we could reliably reproduce it only one machine. It displays some more weird behavior described in following points.
When application window is in restored mode i.e. not maximized, SciChart goes in some state and does not display graph properly and freeze issue happens immediately. But if we maximize window before sending data to graph, Scichart and application behaves normally.
Please see the Q&A on Zoom Not Working on One Single Computer. Does the test-app we posted there reproduce the issue on your computer? If so it is a driver issue and we have a workaround above. If not, please contact firstname.lastname@example.org with any or all info to reproduce the issue and we will investigate asap.
Please login first to submit.