JDK-5026270 : PIT: OGL with Java2Demo fails to show contents in Memory Monitor
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 5.0
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2004-04-03
  • Updated: 2006-09-21
  • Resolved: 2005-03-07
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.
6 betaFixed
Related Reports
Duplicate :  
Relates :  
Tested JDK : /net/jcg-x86-01.sfbay/export3/Java2DBuilds/2d.pit-jcg-win-01-2004-03-31.tiger
Tested OS: WinXP
Vidio: NVIDIA GeForce4 
Test host: i18n-gw700-9      
Running Java2Demo with OGL pipeline enabled on Windows machine,
the Memory Monitor window is blank until close then refressh the window.

- This bug is reproducable on both a Win2000 machine in SQE lab (jfcsqe-earth) running with NVIDIA GeForce2 MX400 (ASUS OEM) board.

- The bug is not reproducable on same machines without OpenGL mode

Steps to reproduce:
1) Set JAVA_HOME to recent Tiger windows build (with OGL support)
2) Launch Java2Demo with OGL option (from demo directory)

$JAVA_HOME\bin\java -Dsun.java2d.opengl=true -jar Java2Demo.jar

3) Notice the Memory Monitor window is blank

EVALUATION This is actually rather mysterious. The bug is also visible in some AWT apps like BezierAnim, where the offscreen image is completely white. Note that no errors are generated (e.g. when creating the pbuffer, or when making a context current to the pbuffer, or when rendering to the pbuffer), so it's tough to see where this problem is coming from. This issue is not reproducible on Windows with Radeon boards, so it appears to be specific to Nvidia's drivers. That said, I'm downgrading this bug, and will try to write a native testcase that reproduces the problem so that we can submit the issue directly to Nvidia. ###@###.### 2004-04-14 This bug appears to be fixed by the single-threaded OGL pipeline project (6219284). That work includes a number of fixes to the whole "shared context" mess, which was the likely culprit of this bug. Under the single-threaded OGL pipeline, the shared context is only used from the single thread, and therefore its usage is much more predictable and correct. Therefore, this bug can be marked as fixed when 6219284 is integrated. ###@###.### 2005-1-27 02:59:17 GMT