-
Bug
-
Resolution: Cannot Reproduce
-
P2
-
1.4.2_11
-
x86
-
windows_xp
Operating System: Windows
OS version: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
Product Name: J2SE
Product version: 1.4.2_08
Hardware platform: Intel(R) Pentium(R) 4 CPU 2.40GHz
Short description: Java GUI freezing on java.awt.MediaTracker.waitForID()
Full problem description:
Our Java GUI application has been freezing on several clients (all Windows XP) occasionally.
It happened intermittently in that it might take several hours, one or two days for the freezing to happen after
the GUI was started. The user just left the GUI open (with several Internal Frame's open as well) without doing
any specific operation before the GUI hung.
Thread dumps from several occurrences are similar and they point to the same place in the Java Swing thread at
the java.awt.MediaTracker.waitForID() method. No explicit dead lock was detected in these thread dumps.
I attached the following information:
1) The DirectX diagnostic tool output on one client that has seen this problem.
2) The full thread dump of the latest occurrence of this issue.
Test case:
Unfortunately we are unable to provide a test case because this problem is intermittent
and we don't know how to reproduce this problem.
Please have some additional information :
1) Is there any specific change which introduced this behaviour like JDK version change or OS change etc.
[Customer comment] No. This version of OS and JRE combination (WinXP and
JRE 1.4.2_08) is the first time use for our current version of
application. However, note this problem only occurs on PCs at one of our
customer sites, but not on others (or our own lab) that also use Win XP
plugin JRE 1.4.2_08. Sure, there might be other things (e.g. hardware)
that might make a difference.
2) Its really fasten the process of debugging, if we have a test case handy,hope we can have the same to reproduce the problem at our end.
[Customer comment] We'll be trying to do that, but we don't know if we can
make it or not because we don't know what might be the cause of the
problem. As mentioned earlier, the GUI starts up and runs fine for hours
or a couple days before it gets frozen.
3) Can you please check with the latest version of jdk 1.4.2 i.e. jdk1.4.2_11
[Customer comment] Yes the same problem is seen with this version of jdk also.
OS version: Windows XP Professional (5.1, Build 2600) Service Pack 2 (2600.xpsp_sp2_gdr.050301-1519)
Product Name: J2SE
Product version: 1.4.2_08
Hardware platform: Intel(R) Pentium(R) 4 CPU 2.40GHz
Short description: Java GUI freezing on java.awt.MediaTracker.waitForID()
Full problem description:
Our Java GUI application has been freezing on several clients (all Windows XP) occasionally.
It happened intermittently in that it might take several hours, one or two days for the freezing to happen after
the GUI was started. The user just left the GUI open (with several Internal Frame's open as well) without doing
any specific operation before the GUI hung.
Thread dumps from several occurrences are similar and they point to the same place in the Java Swing thread at
the java.awt.MediaTracker.waitForID() method. No explicit dead lock was detected in these thread dumps.
I attached the following information:
1) The DirectX diagnostic tool output on one client that has seen this problem.
2) The full thread dump of the latest occurrence of this issue.
Test case:
Unfortunately we are unable to provide a test case because this problem is intermittent
and we don't know how to reproduce this problem.
Please have some additional information :
1) Is there any specific change which introduced this behaviour like JDK version change or OS change etc.
[Customer comment] No. This version of OS and JRE combination (WinXP and
JRE 1.4.2_08) is the first time use for our current version of
application. However, note this problem only occurs on PCs at one of our
customer sites, but not on others (or our own lab) that also use Win XP
plugin JRE 1.4.2_08. Sure, there might be other things (e.g. hardware)
that might make a difference.
2) Its really fasten the process of debugging, if we have a test case handy,hope we can have the same to reproduce the problem at our end.
[Customer comment] We'll be trying to do that, but we don't know if we can
make it or not because we don't know what might be the cause of the
problem. As mentioned earlier, the GUI starts up and runs fine for hours
or a couple days before it gets frozen.
3) Can you please check with the latest version of jdk 1.4.2 i.e. jdk1.4.2_11
[Customer comment] Yes the same problem is seen with this version of jdk also.