-
Bug
-
Resolution: Fixed
-
P2
-
1.4.0
-
None
-
beta
-
x86
-
windows_nt
Sometimes exiting an app mid-stream (via the close box or ctrl-C) can cause
the DirectX system to get corrupted. This means that any other apps dependent
upon ddraw (including java apps that are still running or that are run
after this one exits) may malfunction or underperform.
To reproduce, run a MT-intensive app (such as VolatileDuke in the
src/share/test directory) and click on the close box. Sometimes, after
this abnormal exit, you will notice Windows behaving strangely. For example,
when you minimize a window or pop up a menu and then release it, there
is garbage left on the screen. This happens (I think) only on Win9x
(Windows 95/98/Me).
the DirectX system to get corrupted. This means that any other apps dependent
upon ddraw (including java apps that are still running or that are run
after this one exits) may malfunction or underperform.
To reproduce, run a MT-intensive app (such as VolatileDuke in the
src/share/test directory) and click on the close box. Sometimes, after
this abnormal exit, you will notice Windows behaving strangely. For example,
when you minimize a window or pop up a menu and then release it, there
is garbage left on the screen. This happens (I think) only on Win9x
(Windows 95/98/Me).