JDK-8113621 : REGRESSION: D3D stops rendering after screen lock on Windows
  • Type: Bug
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: fx2.0
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • Submitted: 2011-06-21
  • Updated: 2015-06-16
  • Resolved: 2011-07-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
fx2.0Fixed
Related Reports
Duplicate :  
JDK-8113989 - NullPointerException after windows shows screensaver (program is frozen)
Duplicate :  
JDK-8114376 - NPE in com.sun.prism.d3d.D3DSwapChain.present
Duplicate :  
JDK-8114535 - JavaFX Application GUI missing after restore from hibernate
Duplicate :  
JDK-8114516 - Prism throws exception after starting Task Manager via ++
Description
When I lock screen my laptop with simple app running and unlock it I get 
non-rendering app and a bunch of the following exceptions:

java.lang.NullPointerException
    at com.sun.prism.d3d.D3DSwapChain.present(D3DSwapChain.java:42)
    at com.sun.javafx.tk.quantum.PaintRunnable.run(PaintRunnable.java:241)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
    at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
    at com.sun.prism.render.RenderJob.run(RenderJob.java:29)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at com.sun.javafx.tk.quantum.QuantumRenderer$ObservedRunnable.run(QuantumRenderer.java:70)
    at java.lang.Thread.run(Thread.java:662) 

According to Kirill, this is a regression.
Comments
Verified with b37 . No issues. Also Tested on ATI Radeon HD 5670..
20-07-2011
Returning to fixed state as it is not reproducible with latest graphics scrum
15-07-2011
Still reproducible with b35. java.lang.NullPointerException at com.sun.prism.d3d.D3DSwapChain.present(D3DSwapChain.java:29) at com.sun.javafx.tk.quantum.PaintRunnable.run(PaintRunnable.java:241) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at com.sun.prism.render.RenderJob.run(RenderJob.java:29) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at com.sun.javafx.tk.quantum.QuantumRenderer$ObservedRunnable.run(QuantumRenderer.java:70) at java.lang.Thread.run(Thread.java:662)
15-07-2011
This is because the context gets lost and the swapchain which now uses an RTT loses the RTT.
27-06-2011
You're right. This is Critical.
22-06-2011
This is certainly not a BLOCKER; I might argue that it isn't really even a critical bug (but since that's debatable, I will leave it at critical). First of all, there is a simple workaround for resizable apps (resize the window). Second, screen lock can easily be disabled while running JavaFX tests.
21-06-2011