Charts Crashing: Write lock may not be acquired with read lock held.

[Skeff]

This crash issue over write lock is happening to me SEVERAL times daily and has become beyond problematic and costly.

[DTSSTS]

Update on Data Box - I have been opening the Data Box a few times yesterday and today when I needed to view indicator details etc by mousing over the chart

And as expected I just got my first write lock in over a week running workspace without the data box. I have been mousing over extensively without the data box for a week without a single write lock.

NOT sure it matter Ryan S but I am using a crosshair when mousing over chart

[andyt10s]

With and without the DataBox it still happens. It seems to happen when more than 2-3 days of data are loaded (e.g., NQ, say 5-7 days of data) on non-time based charts (e.g., Renko, NinzaRenko, KingRenko).

[DTSSTS]

andyt10s So you think keep the data load at 3 days could help? on NQ MNQ

[andyt10s]

andyt10s So you think keep the data load at 3 days could help? on NQ MNQ

Yes I am loading only 2-3 days of data for NQ or non-time based charts for that matter. For now it is better than frozen charts and having to restart the machine. I've had to close out trades through the phone app because of this problem.

[DTSSTS]

Well I did change my data series to 2 days loaded MNQ with the data box open and already locked up this morning. Was worth a try. Removing my data box again.

[Lancer]

Has anyone improved or cured the chart freeze issues by uninstalling 8.1.x and reinstalling? Fed up with chart freezing in 8.1.1.7 with read/write lock errors, I tried to go back to a pre SQLite 8.0 version (8.0.26.1). After uninstalling 8.1.1.7, I rebooted, then installed 8.0.26.1, then replaced ca.pem files for CQG data. On NT start, I got an error message "Unable to connect to DB: Index was out of range.". It was becoming a lot of time to fix, so I uninstalled 8.0.26.1, rebooted, then reinstalled 8.1.1.7. Since reinstalling 8.1.1.7, over a week now, there has not been one chart freeze. Who knows if uninstall/reinstall is a total cure, but so far so good. Will post an update if that changes.

[NinjaTrader_RyanS]

Hello,

A fix has been slated for the next public release of NinjaTrader Desktop. At this time there is no planned release date but I will update this thread when a release is available for download.

[zeller4]

Hello,

A fix has been slated for the next public release of NinjaTrader Desktop. At this time there is no planned release date but I will update this thread when a release is available for download.

Thanks Ryan,
how about an update every few days or at least weekly? Thanks.

[NinjaTrader_Christian]

Hello,

our Quality Assurance and our Software Development were finally able to isolate, identify and fix this issue. The fix will be available with next update of NinjaTrader 8.

I apologize for the inconvenience and thanks to everybody here for contributing to identify the issue!

The key information was that the downgrade to R26.1 fixes it!

[Lancer]

Since reinstalling 8.1.1.7, over a week now, there has not been one chart freeze. Who knows if uninstall/reinstall is a total cure, but so far so good. Will post an update if that changes.

It's definitely an improvement, but not a total cure. Got the first chart freeze today right at the regular session close during the highest trade rates with chart lag. Task Manager end task required to close frozen NT.

Great to hear that a fix will be in the next release.

[Lancer]

Update - I'm still getting chart freezes. No pattern to it; could happen at any time, while in use or unattended. Yesterday it froze once, and today it froze once again, and before yesterday there were freezes as well. Typical behavior of the active symbol tab charts all stopping while the inactive (non-visible tab symbols) charts are all running normally, with Market Analyzer, DOM, and T&S all running normally. But click a few things, or start to open menus, etc., and the whole workspace freezes, and Task Manager > End Task is required to close NinjaTrader. A fix for this can't come soon enough.

Fortunately I have an old lifetime license, and can still use NinjaTrader 7.

[kevinenergy]

Is there any update on when this fix is going to be released? Rather than waiting for the next general release, could a patch-release not be created that only has this fix in it, given that this is such a high-impact issue for so many users?

[yertle]

Hi,
I'm having troubles with the read/write lock errors.

It's related to an indicator I've built, which uses multiple/ many data series.
It freezes/ and displays the error with the indicator loaded and when I zoom in/ out of the chart or pane across.
- I just went back to version 26 and still got the error.
So I think it's specific to my code. & Not the general issue discussed above.

( I just re-wrote the whole thing from scratch with more simplicity & it's still causing the error)

ChatGPT suggested using lock blocks to manually specify how the memory is used.

Does anyone have an example of this that I can refer to?
- is it necessary? Or is it the wrong approach?

Edit: My solution was using circular buffers, instead of arrays

Cheers,

[zeller4]

Hi,
I'm having troubles with the read/write lock errors.

It's related to an indicator I've built, which uses multiple/ many data series.
It freezes/ and displays the error with the indicator loaded and when I zoom in/ out of the chart or pane across.
- I just went back to version 26 and still got the error.
So I think it's specific to my code. & Not the general issue discussed above.

( I just re-wrote the whole thing from scratch with more simplicity & it's still causing the error)

ChatGPT suggested using lock blocks to manually specify how the memory is used.

Does anyone have an example of this that I can refer to?
- is it necessary? Or is it the wrong approach?

Cheers,

Yertle,
This has been happening to numerous users per this thread as you can see. I personally have numerous custom indicator codes but this is happening to empty charts when I use free bar types such as UniRenko and NinzaRenko bars. You might look into a test for yourself to see if it's doing that in your situation with bare charts. Search for the free bar types on your browser. Hopefully, you can report back to this thread with your results.