|03-01-2011, 03:28 PM||#1|
Join Date: Apr 2010
Debug/Symbol Builds for gluegen-rt.dll, jogl.dll, jogl_awt.dll, jogl_cg.dll?
We're battling a "committed virtual memory" leak. This value is reported by jconsole on the "VM Summary" tab. This value is also equivalent to the Windows Task Manager "Virtual Memory Size" (Task Manager->View->Select Columns->Memory Commit Size->Enable Checkbox); on Windows 7 it is called "Commit - Size"). After 13 days our application, jconsole reported the committed virtual memory as 1.6GB and eventually crashed with EXCEPTION_ACCESS_VIOLATION (0xc0000005) emitting hs_err_pid3104.log. In case you're wondering, we've already fixed a few Java heap memory leaks but now we're down to this C/C++ leak.
We're still trying to isolate the source of the leak. I'm guessing the leak is caused by our Java code forgetting to release a resource. Since this leak shows up in the C/C++ side of the Java Virtual Machine, debug/symbol build version of all the involved C/C++ code would be very helpful. Does the World Wind development team have debug/symbol builds for the following DLLs for say Windows XP 32-bit (really any flavor of Windows, we support most of them after XP)? Such builds would let me isolate the source using Rational Purify etc.
I looked on the World Wind wiki and searched through lots of posts but haven't found anyone asking this question.
Does anyone have tips on locating C/C++ leaks when code is running on a world wind "stack" (java.exe/jogl/videodriver)? I found this link fairly helpful http://www.oracle.com/technetwork/ja...499.html#gbyvk
I've attached the hs_err_pid3104.log to this post. Anyone have an idea what might be allocating the 16MB chunks shown at bottom of the cpp-heap-detail-day10.png attachment?
Last edited by buzz3791; 03-03-2011 at 02:27 PM. Reason: add pictures of leak
|committed virtual memory, jogl, memory leak|
|Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)|