JDK-8126218 : Canvas: Updates to the Canvas can be lost in some cases
- Type: Bug
- Component: javafx
- Sub-Component: graphics
- Affected Version: 7u6
- Priority: P3
- Status: Resolved
- Resolution: Not an Issue
- Submitted: 2012-06-21
- Updated: 2015-06-17
- Resolved: 2012-06-29
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.
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.
| JDK 7 |
|---|
7u6Resolved  |
Related Reports
|
Relates :
|
Description
The PG sync mechanism for canvas passes the reference to the growable data buffer down to the NGCanvas. This reference overwrites the existing buffer reference. The buffer is not consumed at sync time but only when the NGCanvas is rendered. This means that if a new buffer is passed down at sync time before the old buffer is rendered, the graphics commands in the old buffer will be lost. This is a problem because the canvas is defined as persistent.
Comments
|