When destruction of a static GDIHashTable happens, the table is emptied which causes AwtGDIObject::Decrement calls, which in turn use an objectCounterLock critical section. This variable is also static and it might be already destroyed by the time. The consequences of locking a destroyed CriticalSection are undefined and unclear - for example, this have probably caused 6367631.

We should fix this, and also study the native code for similar risks.