Write lock may not be acquired with read lock held

[buildorbust]

This is because used Dispatcher.Invoke() instead of Dispatcher.InvokeAsync()?

[NinjaTrader_ChrisL]

Hi buildorbust, thanks for your question.

Our help guide claims you can get a deadlock if you use Invoke rather than invokeasync:

https://ninjatrader.com/support/helpGuides/nt8/?multi-threading.htm

Do you get the problem when you use InvokeAsync rather than just Invoke? If so we would need more details on the code being run.

I look forward to assisting.

[saturntd]

Hello,
I'm getting the attached errors on a fully managed strategy.
I'm not using any custom events that override the Ninja events.
What is the procedure to handle this issue?

[NinjaTrader_ChrisL]

Hi saturntd, thanks for posting.

The second message means the process (NInjTrader) has run out of PC memory. Do you get this consistently or only randomly when other applications are open? Please also make sure there is at least 2GB of paging file memory set up on your Windows installation:
https://mcci.com/support/guides/how-...pagefile-size/ (publicly available link)

Kind regards,
-ChrisL

[saturntd]

Chris,
Thanks for the response.
I'm going to increase system memory. It is usually almost all used up. The paging was already higher than recommended.