Memory Leak in IRIX Texture Memory Management???

New Message Reply Date view Thread view Subject view Author view

Linda Rae (lrae++at++indy3.gstone.com)
Wed, 22 Oct 1997 12:23:24 -0700


Hello all:

I am hoping the problem that I am describing is user induced; but I will be
wecoming all inputs...

My app runs on IRIX6.2 on an Onyx w/ 256M memory. One platform has 2 RM4
boards and 1 platform has 2 RM5 boards. The app is loading a terrain
database that contains a total of 64M of texture. I am not currently doing
any active database management (like with pfDBase). I am letting IRIX/
Performer handle the Texture memory management as my app moves through the
database.

The problem is that there an apparent memory leak. If I run my app with a
terrain database that contains < 4 MB texture. This memory leak does not
occur. Additionally this memory leak does no occur on my O2. (yes, yes, I
know the O2 has different graphics HW etc.. ) Which is why I think that
this problem I am experiencing is down in the RasterMemory memory management
scheme. Additionally this problem can be reproduced on any similiar HW
platform. Some other obvious observations include that leakage rate
accelerates as I increase the number of different camera views drawing the
Terrain view. Is there a patch(s) that I am not aware of?? Has anyone
else attempted overload the RM memory w/out activly managing the database
(e.g. pfDBase)....

Any insight/ opinions etc will be welcome...

Thank-you.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Linda Rae 4950
Murphy Canyon Rd
GreyStone Technology San Diego, CA 92123
lrae++at++gstone.com
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
=======================================================================
List Archives, FAQ, FTP: http://www.sgi.com/Technology/Performer/
            Submissions: info-performer++at++sgi.com
        Admin. requests: info-performer-request++at++sgi.com


New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Mon Aug 10 1998 - 17:56:07 PDT

This message has been cleansed for anti-spam protection. Replace '++at++' in any mail addresses with the '@' symbol.