On 2003.03.04 20:00 Ian Romanick wrote:
Pawel Salek wrote:Today, I have run a molecular visualisation program on a RNA strand (I usually deal with slightly smaller molecules) and I was surprised when I noticed that the process occupied more than 200MB of memory. Disabling the visualisation mode reduced the memory usage to mere 8MB. So, the 200MB memory is basically used by a very simple display list generation that for the molecule in question creates a 1336 GL_QUAD_STRIP's with total 34736 glVertex3f vertexes (26 vertexes per strip) and 1212 GL_TRIANGLES with 465408 total glVertex3fv vertexes (384 per glBegin/glEnd group) - which seem like reasonable values.
Is the application using display lists? There is a know problem where display lists can use a lot more memory than they should. If the app does use display lists and you have access to the source, could you modify it to not use display lists? I'd be curious to see if the memory usage goes down.
Affirmative. I do have access to the source and disabling the display list generation and doing direct rendering instead reduces the memory usage to the base level (8MB). I am sure plenty of people would love to have this issue fixed since it basically renders display lists useless for non-trivial applications (but I am sure you guys know that, too).
Thanks for help!
Pawel
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger for complex code. Debugging C/C++ programs can leave you feeling lost and disoriented. TotalView can help you find your way. Available on major UNIX and Linux platforms. Try it free. www.etnus.com
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
