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

[RideMe]

Perhaps the community could list their possible "suspects" to narrow down the culprit. The only third party indicators that I am using are the following:

1. NinzaRenko Bars - downloaded from Ninza.co site.
2. McGiinley Dynamic - downloaded from the NinjaTrader Ecosystem site.
3. MACrossBuilder - downloaded from the NinjaTrader Ecosystem site.

The issue typically arises during volatile / fast markets. However, this is not always the case. Sometimes, simply hovering my cursor over the chart seems to trigger the lock-up.
I use 3 monitors (all 4K). I typically have 7 to 8 charts open - all will be on the same futures contract (NQ, ES or RTY).

My computer was built / designed for trading by Falcon Trading Computers. Not sure this is relevant, but who knows.

Recently (last 4 to 5 months), I did a complete reinstall of Ninjatrader. Rebuilt workspaces from scratch, etc.. This did not resolve the issue.

Any insight would be appreciated.

[DTSSTS]

My issues are most always hovering over a chart. I only have 2 charts open. I have experienced with UniRenko and another off standard candle. UniRenko was the worst. I have occasionally had the lock without realizing when it actually started. The write lock warning does not pop up until you are exiting the platform to restart, You cannot exit positions until restate OR best is to go to the broker account directly and close. Many times the restart takes for ever or never starts until I end task again, then start in a Safe Mode (no workspace) close immediately, then restart again. At this point the strategies are all missing from control center and must be reloaded from scratch.

THE ABOVE falls in the FWIW category.

[backtester831]

Sounds like it's happening more frequently with custom bar types, NinzaRenko and UniRenko. I believe in both case, the open of the bars is artificial and not actual open of the bar, wonder if that has anything to do with it.

[RideMe]

I agree with backtester831....from what I have read, seems like it could have to do with renko bars, and perhaps the artificial open / close of the bar.

[jculp]

@NinjaTrader_RyanS I noticed that in one of your posts in this thread, you said you could not reproduce with Renko bars. However, that was in response to a comment about Unirenko bars; specifically a bar-type updated for NT8 by Chelsea. Did you test with that bar-type? There is a difference between basic renko bars, and the unirenko-type bars which comments in this thread are referring to. Does NT consider the "Chelsea-unirenko" to be a 3rd party add-on? And therefore you excluded it from your testing?

[Taggart]

+1 for using UniRenko with 4-5 charts. Crashes 3-6 times a day. Zero crashes with 8.0.26, Glad I bought a lifetime license a month before this change.

[Lancer]

In my case, I am using a standard candle bar type provided in the NT 8.1 download; nothing Renko or custom. Today, NT froze after-hours while the computer was unattended, so there was no user input at the time of the freeze. Unattended freezes happen about as often as when I am at the desk moving the mouse over a chart. There is no "set of steps" that relate to the problem that I can see. What is running on NT when it freezes is the same as what is running on NT when it does not freeze. Log and trace file event logging is completely inadequate and useless for logging these freeze events; nothing related to these freeze events is ever written to log and trace files.

[jculp]

Lancer If you are getting the deadlock error with only base NT8 features, no custom indicators or bar-types or 3rd-party add-ons, please send your results to NT support. Currently, they are claiming that they have not seen any example of writelock/deadlock errors occurring with only base NT8 code. A real-life example might get them to move away from that position.

[DTSSTS]

In my opinion this really does not matter

"deadlock error with only base NT8 features, no custom indicators or bar-types or 3rd-party add-ons,"

" any example of writelock/deadlock errors occurring with only base NT8 code."

There is a huge user group and third party vendors that are a big part of why we use NinjaTrader. Their changes have let us all down and their continued unwillingness to fix what they broke is really so unacceptable to most of us.

There does not seem to be any real effort to solve this issue.

[Lancer]

Hi Phil.

Ninjatrader are in denial about this problem. Most people are just manually installing the certificate and staying on 8.0.26.1

I've attached the cert.

After you have installed 8.0.26.1,
Close Ninjatrader, then replace the "ca.pem" file in:


C:\Program Files (x86)\NinjaTrader 8\bin
C:\Program Files (x86)\NinjaTrader 8\bin64

with the one in the attached zip file.

Then restart Ninjatrader and enjoy a crash-free experience on 8.0.26.1

Finally gave up on productivity-killing randomly-freezing NT versions after 8.0.26.1 and attempted to roll back to 8.0.26.1, but am getting an "Unable to connect to DB" error message. "Unable to connect to DB: Index was out of range. Must be non-negative and less than the size of the collection. Parameter name: Index"

I uninstalled 8.1.1.7 (in Program Files), rebooted, installed 8.0.26.1 (in Program Files (x86)), did the ca.pem replace in bin and bin64 for CQG per kevinenergy, and started NT. When the NT startup screen process list gets to "Initializing Database", the Unable to connect to DB error screen pops up. After clicking OK, the startup process ends and the NT startup screen closes.

So obviously I missed a step somewhere. What is the step-by-step procedure to go back from 8.1.1.7 to 8.0.26.1?

[DTSSTS]

To be clear I am not running 8.0.26.1 yet. (Keep hoping Ninja will step up, but that does not seem to be going to happen)

This is the first mention I have seen about replacing a file. Is CQG a brokerage? If so are you actually using that. IF NOT, maybe put back the original to see if that fixes this for your needs.

Good Luck

[Lancer]

DTSSTS, replacing the ca.pem files may only be applicable to CQG/Continuum subscribers (for live market data and order routing). Here is the 6/20/23 "must update" notice:

[kevinenergy]

Hey Lancer you need to delete Documents/Ninjatrader before you install

the later versions of Ninjatrader have upgraded the database and settings etc so 8.0.26.1 can’t connect to the new DB.

I’m still using 8.0.26.1 and I’m perfectly happy with it. It’s great to have confidence in the platform which I don’t have with the later versions

[Lancer]

Rather than messing with the whole NinjaTrader folder that includes everything, what about deleting just the db folder?

[kevinenergy]

Lancer We don’t know what other changes have been made to the Ninjatrader config files.


do you have any old backups you can restore? Alternatively, rather than deleting the directory. Try renaming it. To “Ninjatrader 8 - backup” then reinstall 8.0.26.1

once you have 8.0.26.1 working you could try copying the Templates folder over. this would restore much of your config. Make sure you close Ninjatrader first.

If I was you I would just build my environment from scratch rather than risk any further problems.