-
Bug
-
Resolution: Fixed
-
P3
-
7u6
-
java.runtime.version=1.7.0_06-ea-b17
javafx.runtime.version=2.2.0-beta-b16
nvidia gtx460
win7
To reproduce this issue:
- use the same sample test app asRT-23311
- run the app with java -client switch rather than the java -server switch
- while the app is running press Ctrl+Alt+Del (which on win7 brings up a screen with a bunch of options).
- press cancel at the win7 options screen to return to the windowing system.
- app will have died with an OutOfMemoryException
The workaround documented in the sample test app (writing data to a writable image then putting the image to the canvas rather than directly setting the pixels in the canvas via a pixelwriter) forRT-23311 also solves this issue as well - though again I have no idea why.
- use the same sample test app as
- run the app with java -client switch rather than the java -server switch
- while the app is running press Ctrl+Alt+Del (which on win7 brings up a screen with a bunch of options).
- press cancel at the win7 options screen to return to the windowing system.
- app will have died with an OutOfMemoryException
The workaround documented in the sample test app (writing data to a writable image then putting the image to the canvas rather than directly setting the pixels in the canvas via a pixelwriter) for
- relates to
-
JDK-8092801 [Canvas] Canvas buffers commands indefinitely when it isn't visible leading to Out of Memory Exception
- Resolved
-
JDK-8103438 Canvas should clear its buffered commands on certain clearRect, fillRect calls
- Resolved
-
JDK-8102206 JavaDocs for new Canvas node
- Closed
-
JDK-8093950 [D3D] Re-enable DirectX 9Ex to avoid losing textures when surface lost
- Resolved