JDK-6319745 : PIT: OGL: NPE is thrown when an application using BufferStretegy + FS terminates, Win32
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 6
  • Priority: P3
  • Status: Open
  • Resolution: Unresolved
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2005-09-03
  • Updated: 2012-01-16
Related Reports
Relates :  
JDK-6538511 - NPE when removing one of the monitors at runtime, win32
Description
I am running an application that uses BufferStrategy with 2 buffers to do page flipping in a 640X480 display mode. When I am running this application with OpenGL flag enabled, I am getting a NPE when the application terminates. 

This is reproducible only with the following PIT build on WinXP. Not reproducible with Mustang-b49.
java version "1.6.0-internal"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.6.0-internal-java2d_28_aug_2005_21_23-b00)
Java HotSpot(TM) Client VM (build 1.6.0-ea-b49, mixed mode)

Here is the exception:
Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException
at sun.awt.image.VolatileSurfaceManager.displayChanged(VolatileSurfaceManager.java:310)
at sun.awt.SunDisplayChanger.notifyListeners(SunDisplayChanger.java:102)
at sun.awt.Win32GraphicsEnvironment.displayChanged(Win32GraphicsEnvironment.java:115)
at sun.awt.windows.WToolkit$4.run(WToolkit.java:727)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)

This is not reproducible with d3d, ddraw modes on the same system. The WinXP machine that I used is having a NVidia GeForce4 MX4000 video card with (77.77) nvidia driver.

Run the attached test on WinXP. You would notice the display modes changes automatically. Wait for the application to terminate. You would notice the above exception on the console. This exception is occuring intermittently. So you may have to run the app a few times to reproduce the bug.
Comments
EVALUATION This has the same stack trace as reported in 6325718, so the problems are most likely related (even though it is occurring on different pipelines). I'll leave both bugs open until we can figure out if it is the same root cause.
23-09-2005