JDK-8120885 : 3D Data validation
  • Type: Bug
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: 8
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2012-11-29
  • Updated: 2015-06-17
  • Resolved: 2013-10-08
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.
JDK 8
8Fixed
Related Reports
Blocks :  
JDK-8101906 - Wire up 3D public API to the d3d pipe
Relates :  
JDK-8103114 - FX 8 3D: Need to validate Mesh's data size
Description
D3D mesh has build-in data validation in  buildGeometry method. It validates all indices and faces area to prevent native crash.
However it is requred to validate input data during FX->NG sync stage. It will prevent AIOOB exceptions during picking computations.
The best is to track this in the JIRA.

There is no need to validate predefined shapes.
Comments
Test with: attached test MeshViewUpdate.java Unit Test: TriangleMeshTest.java
08-10-2013
Reassign to Yao since she has started some of this work.
27-09-2013
It's better to validate when the data is changed, if possible. In cases where that is impractical then what Kirill is suggesting is a good place to do it. If the data is validated at the FX->PG sync time, then the only thing that can be done with bad data is to skip rendering of the primitive. There is no user code on the stack and no way to throw an exception back to the user. Also, changing the priority to Major, since it isn't blocking any testing or wiring up. It must be done before feature freeze, though.
30-11-2012