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

[Lancer]

Renaming the db folder and letting NT 8.0.26.1 recreate it did not work, and resulted in the same database error message during startup and failure to start. To rebuild from scratch the NinjaTrader 8 folder /NT environment, developed over many years, would be a time and cost prohibitive amount of work, so rebuilding is not an option. Next, I'll try renaming the Documents/NinjaTrader 8 folder, reinstalling 8.0.26.1 to create a new NinjaTrader 8 folder, and see about moving or importing files from the renamed folder to the new one, including replacing the ca.pem files for CQG connectivity. There must be some way to nondestructively and efficiently revert to a pre-SQLite version. No doubt NT developers have a documented procedure for it. NT support staff, hello?

[NinjaTrader_RyanS]

Hello all,

We have now reproduced this issue on our end using a combination of Kagi charts within a workspace. Our QA team is looking into this issue/behavior further at this time.

The issue seems to only occur with bars that do not use a set number of ticks or time, such as Renko, Kagi, and UniRenko.

Thanks for your patience while we investigate this further.

[Lancer]

RyanS, bars that do not use a set number of ticks or time also includes Volume charts. I'm seeing the issue with Volume charts.

[jculp]

Lancer I was able to successfully revert to v26 by importing a backup made before my "upgrade" to v28. Immediately after fresh install of 8.0.26, I imported the backup; otherwise, I got the db error msg. Of course, not helpful if you don't still have a backup made with v26. See this thread for more discussion: https://forum.ninjatrader.com/forum/...rt-to-8-0-26-1

[DTSSTS]

RyanS

Maybe Ninja could give us an escape key to unlock without the need to force shutdown and in many cases all loaded strategies in the Control Center had to be re applied. Big waste of time and open positions cannot be closed as the system is unresponsive to pretty much any thing.

Just happened again this morning and as usual was during mouse over the chart to view data in the Data Box

Thanks

[kevinenergy]

I mentioned previously on this thread I had a feeling it might be related to the databox... Most of my crashes seems to coincide with databox use.

RyanS

Just happened again this morning and as usual was during mouse over the chart to view data in the Data Box

Thanks

[DTSSTS]

I missed that or forgot, I will try to run my workspace without data box for a bit and see if I continue to write lock.

[DTSSTS]

Update 2 and half sessions no write lock with NO Data Box I will continue without Data Box into next week and see if this continues to be the case or just luck.

[kevinenergy]

Ryan,

It is great news that this issue has finally been reproduced at your end. Would you mind sharing details of the root-cause once it is established? I've been a prolific bug hunter on Ninjatrader 8 since it was in beta, but I could not get a reproducible scenario on this one so curious to know what the cause was.

Also when the fix is deployed could we get a new 8.0.X and a new 8.1.X version?

Hello all,

We have now reproduced this issue on our end using a combination of Kagi charts within a workspace. Our QA team is looking into this issue/behavior further at this time.

The issue seems to only occur with bars that do not use a set number of ticks or time, such as Renko, Kagi, and UniRenko.

Thanks for your patience while we investigate this further.

[balltrader]

consider monitoring Private Bytes consumption of NinjaTrader.exe with a tool like Process Hacker,
and tab=.NET performance,
Categories: .NET CLR LocksAndThreads,
to watch activity during mouse hover of Data Box.

[DTSSTS]

I does not lock up with mouse over of the data box, I lock up with mouse over of the chart. kevinenergy had suggested that he thought had something to do with the data box. So I removed the data box from my workspace as a test.

[zeller4]

Hello all,

We have now reproduced this issue on our end using a combination of Kagi charts within a workspace. Our QA team is looking into this issue/behavior further at this time.

The issue seems to only occur with bars that do not use a set number of ticks or time, such as Renko, Kagi, and UniRenko.

Thanks for your patience while we investigate this further.

Hello Ryan S., any update on this???

[NinjaTrader_RyanS]

Hello,

So far I do not have any updates from our Quality Assurance team, but once I receive further information on fixes or possible releases I will update this thread.

[DTSSTS]

Ryan S please tell the QA department about the Data Box could be related. kevinenergy had mentioned that way back and reminded me of his post last week. I get the write lock multiple times per day when mousing over my chart and only then. I platform must be shutdown by task manager when this happens. I removed my Data Box and for several days tested without issues.

Today I was mousing over charts extensively (likely over 100 times) and never locked up. I will reapply the Data Box in the next day or two and report back. I am agreeing with kevin that is the problem.

[NinjaTrader_RyanS]

Hello,

I've added this may be related to our QA team and our workspace that replicated the issue has a data box loaded as well. Thanks for the feedback on this item.