-
Bug
-
Resolution: Fixed
-
P4
-
1.4.0, 1.4.1_02
-
None
-
07
-
x86
-
windows_nt, windows_2000
-
Verified
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2054638 | 1.4.2 | Chet Haase | P4 | Resolved | Fixed | mantis |
When a machine is running as a connected NetSupport client, it is possible
to hang during any graphical Java app startup in Win32GraphicsEnv.initDisplay().
In particular, this happens when the client is set to 32 bpp display depth.
To reproduce this bug, install a demo of NetSupport manager
(www.netsupport-inc.com) on two machines: one will be the client (where the
problem will appear) and one will be the controller which connects to the
client. Using the client configurator, name the client machine. Using the
controller, connect to that client. (Be sure to run in 32bpp display
depth; and don't switch display modes while connected in NetSupport; this
crashed my system consistently (nothing to do with Java on this one...)).
Now, on the client (either locally or remotely), run a Java app and note that
it hangs before displaying anything. If you type ctrl-Break in the console,
you will probably see one of the threads hung in Win32GraphicsEnv.initDisplay().
- backported by
-
JDK-2054638 infinite loop in Win32GraphicsEnv.initDisplay() when NetSupport is running
-
- Resolved
-
- duplicates
-
JDK-4916704 simple java awt program hangs in constructor for J2SE1.4.1_02/1.4.1_03
-
- Closed
-