Possible hash synchronization bug exposed by AWT?

Wed Jul 21 23:34:00 GMT 2004

We've noticed an intermittent synchronization problem that occurs 
(occasionally) when starting AWT applications on i686-pc-linux-gnu, 
possibly only on multiprocessor/hyperthreading systems.
What happens is that an IllegalMonitorStateException ("current thread 
not owner") is thrown from _Jv_MonitorExit when leaving 
EventQueue.getNextEvent() - a seemingly impossible situation. When this 
occurs there is another thread blocked in EventQueue.postEvent() waiting 
for the lock.
I've posted a bug report with more details here:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16662
Any ideas? Has anyone else seen this?
Regards
Bryce