0568c76a88
When an object is removed, its scripts are stopped and then the thread running them is aborted if stop takes too long.
However, it appears that aborting a thread at just the wrong moment when it is obtaining a ReaderWriterLockSlim lock can leave this lock in an inconsistent state.
One symptom of this is that mono leaps to 100% cpu and a vm thread dump reveals lots of threads waiting for a ReaderWriterLockSlim lock without any thread actually holding it.
This is probably the same problem as encountered originally in commit
|
||
---|---|---|
.. | ||
ApplicationPlugins | ||
Capabilities | ||
ConsoleClient | ||
Data | ||
Framework | ||
Region | ||
Server | ||
Services | ||
Tests | ||
Tools |