JDK-8117478 : ImageView fails to displays fragment of large image with d3d pipeline
  • Type: Bug
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: 7-pool
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2011-09-20
  • Updated: 2015-06-17
  • Resolved: 2012-01-23
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.1Fixed
Related Reports
Blocks :  
JDK-8097738 - remove scaling from NGImageView might improve performance
Relates :  
JDK-8101029 - Refactor imageview code.
Relates :  
JDK-8127241 - Stitching issues when using large images
Relates :  
JDK-8127047 - Make NGImageView's ability to display a fragment of a large image re-usable by NGWebView
Description
Run the attached test application with the attached 10032x32.png image with the j2d and d3d pipelines. With the j2d pipeline, the application window will display a small red square with the "OK" text in it, see the attached j2d.png screenshot. With the d3d pipeline, the application window will be empty, see the attached d3d.png screenshot.
Comments
changeset 15326 (f5fdc31e5050) fix : RT-17041 ImageView - huge image support
23-01-2012
I will provide the fix that can remain while the other bug is being worked on that will fix this problem.
10-11-2011
duplicate of http://javafx-jira.kenai.com/browse/RT-17738
10-11-2011
Put back in Presidio Updates pool for a future 2.x release.
28-10-2011
Assign to Joe based on Kirill's findings. Note that this is not a regression or a recent behavioral change, so I am going to lower the priority to P4. We will likely target it for 2.1.
12-10-2011
The bug is not related to D3D directly, it happens because we are limited in texture size and is reproducible in OGL as well. The affected part is NGImageView.render - complex part which subdivide image.
12-10-2011
The underlying reason of this bug is that viewports introduced by Changeset: 6308 (d28654f18855) fix RT-7819 Prism image Viewports do not support images bigger then maximum texture size.
06-10-2011
See the Environment field: Prism pipeline init order: d3d Using t2k for text rasterization Using dirty region optimizations Prism pipeline name = com.sun.prism.d3d.D3DPipeline Loading D3D native library ... succeeded. OS Information: Windows 7 build 7601 D3D Driver Information: NVIDIA NVS 3100M \\.\DISPLAY1 Driver nvd3dum.dll, version 8.17.12.6802 Pixel Shader version 3.0 Device : ven_10DE, dev_0A6C, subsys_21D417AA Direct3D initialization succeeded (X) Got class = class com.sun.prism.d3d.D3DPipeline D3DPipeline:getInstance(), d3dEnabled=true Initialized prism pipeline: com.sun.prism.d3d.D3DPipeline
06-10-2011
Vasily, what hardware do you use ? What -Dprism.verbose=true prints ?
06-10-2011