This is the mail archive of the java@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Possible hash synchronization bug exposed by AWT?


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]