12cebb12d5
This seems to be a particular problem with ReaderWriterLockSlim, though other locks can be affected as well. It has been seen to happen when llDie() is called in a linkset running more than one script. Alleviation here means supplying a ScriptInstance.Stop() timeout of 1000ms rather than 0ms, to give events a chance to complete. Also, we check the IsRunning status at the top of the ScriptInstance.EventProcessor() so that another event doesn't start in the mean time. Ultimately, a better solution may have to be found since a long-running event would still exceed the timeout and be aborted. |
||
---|---|---|
.. | ||
ApplicationPlugins | ||
Capabilities | ||
ConsoleClient | ||
Data | ||
Framework | ||
Region | ||
Server | ||
Services | ||
Tests | ||
Tools |