The issue is I need to lock off an object so that calculations aren't being affected while it's being updated. The problem is a race condition is easily created when we try to acquire our lock, while NT is trying to lock something else that another thread already has the lock to.
What is the appropriate object to try to acquire a lock on to avoid this?
See the screenshot here.
To recreate the issue, simply use the sample indicator attached and either run it in Simulated Data or live marketdata and run for a couple minutes (use a fast chart, like a 2 second chart).
Any insight would be greatly appreciated, thanks,
Jeremy
SharkIndicators
Comment