Procedural-Landmass-Generation
Procedural-Landmass-Generation copied to clipboard
Lock .Dequeue()?
Should there be a lock (dataQueue){ ... } around .Dequeue() in ThreadedDataRequester.cs > Update() method? As there is a lock for Enqueue()? I have seen the resulting parameter be null in cases with very high terrain chunk numbers, but only intermittently, which leads me to this method... threadInfo.callback(threadInfo.parameter);
I agree. If you need to lock for one you should lock for both.