-
Bug
-
Resolution: Fixed
-
P3
-
1.4.0
-
None
-
beta2
-
x86
-
windows_nt
The awt trace utilities (enabled only by special build and runtime
parameters) do not behanve correctly in the event of the application
exiting. In particular, it seems that calling JVM_* functions after
PROCESS_DETACH time is a Bad Thing on win9x.
This problem can occur whenever there is a call to DTRACE_PRINTLN()
on a trace-enabled build and run after DllMain() is called with the
PROCESS_DETACH message. Some of the methods that assist in shutting
down the graphics system make these calls and can cause this
problem. For example, we currently release the ddraw resources
at this time, to avoid holding the ddraw lock after app exit; any of these
methods might have DTRACE_PRINTLN calls in them.
The result of this problem is that the JVM_* call to get the
awt trace mutex will hang, so the trace command will not return,
DllMain() never exits, so the app never completes and, in some
situations, ddraw is left in an unsteady state and can hang the system.
- relates to
-
JDK-4672111 java_g hangs on exit on windows platforms
-
- Resolved
-