JDK-6796971 : Deadlock in XAWT
- Type: Bug
- Component: client-libs
- Sub-Component: java.awt
- Affected Version: 6u12
- Priority: P2
- Status: Closed
- Resolution: Duplicate
- OS: generic
- CPU: generic
- Submitted: 2009-01-22
- Updated: 2011-01-19
- Resolved: 2009-01-23
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 |
|---|
6u14Resolved  |
Related Reports
|
Duplicate :
|
Description
While testing the Java Plug-In on Linux, the attached deadlock in the XAWT was provoked. It occurred when the Java Console was set to show, when the JRE used was an internal build, and upon loading the Clock applet from http://java.sun.com/products/plugin/1.5.0/demos/applets/Clock/example1.html . The deadlock is intermittent and I haven't reproduced it since. However, the thread dump clearly shows the deadlock so hopefully it can be fixed via code inspection.
Comments
|