summaryrefslogtreecommitdiffstats
path: root/doc/userguide/index.html
diff options
context:
space:
mode:
authorKenneth Russel <[email protected]>2005-06-22 08:05:55 +0000
committerKenneth Russel <[email protected]>2005-06-22 08:05:55 +0000
commite9b806b277428b74a51afb5e076afe7dfabb26d4 (patch)
tree779d537277a577c7fb8161ed4013a88026933eb0 /doc/userguide/index.html
parent9cf58f1f404b069ab3f13f80daa774b7da4ff8e2 (diff)
Fixed Issue 166: Memory leak with ATI Mobility Radeon 9700
Worked around memory leak in ATI's OpenGL drivers by adding system property -Djogl.GLContext.nofree which users can specify on the command line. There is no good general-purpose workaround for this bug which works well on all hardware and in all kinds of applications. Issues may remain if this workaround is used and if the GLCanvas is removed and re-added to its parent container. Use at your own risk. Also cleaned up Windows ChoosePixelFormat code path; made sure PIXELFORMATDESCRIPTOR was completely filled out. git-svn-id: file:///usr/local/projects/SUN/JOGL/git-svn/svn-server-sync/jogl/trunk@306 232f8b59-042b-4e1e-8c03-345bb8c30851
Diffstat (limited to 'doc/userguide/index.html')
-rw-r--r--doc/userguide/index.html19
1 files changed, 19 insertions, 0 deletions
diff --git a/doc/userguide/index.html b/doc/userguide/index.html
index 1ef37540b..03880cbd4 100644
--- a/doc/userguide/index.html
+++ b/doc/userguide/index.html
@@ -549,6 +549,25 @@ future JOGL release and plan to have better interoperability by the
time JDK 6.0 is shipped.
</P>
+<P>
+
+There is a serious memory leak in ATI's OpenGL drivers which is
+exhibited on Windows XP on Mobility Radeon 9700 hardware. It's
+possible it will be present on other hardware as well though it was
+not reproducible at the time of this writing on desktop Radeon
+hardware or older ATI mobile chips. The bug is documented in <A
+HREF="https://jogl.dev.java.net/issues/show_bug.cgi?id=166">JOGL Issue
+166</A> and a bug has been filed with ATI. You can confirm the
+presence of the bug either with the test case in that bug report or by
+simply running the Gears demo; if the process size grows over time in
+the Task Manager, the memory leak is present on your hardware. For the
+time being, you can work around this memory leak by specifying the
+system property <CODE>-Djogl.GLContext.nofree</CODE> on the command
+line when launching your JOGL applications. There is no good
+general-purpose workaround for this bug which behaves well on all
+hardware.
+
+</P>
<H3> Solaris, Linux (X11 platforms) </H3>