Re: The infamous dbase paging memory leak

New Message Reply Date view Thread view Subject view Author view

Scott Herod (herod++at++aspen.evt.com)
Fri, 23 Apr 1999 16:04:31 -0600

Hear! Hear! I'm all for having performer completely
removing the textures. Last Summer I beat my head against
this one for weeks because there seems to also be an
OCTANE bug which caused texture handles to become confused
after awhile. The result was that we would occasionally
see corrupted textures showing up on objects. Since
we now delete glhandles (after verifying that there is
a valid graphics context) I have not seen the corruption
problem so I don't know if it has carried into IRIX 6.5.

Scott Herod
scott++at++evt.com

P.S. I wish I had been aware of the fltSharedPalette last
week. We call in model loaders at run time from a dso
which makes it rather hard to account for every possible
loader configuration. In addition it would require us
to link in every possible loader.

Angus Dorbie wrote:
>
> This still won't do it, it's the gl handles you need to delete from the
> draw process. Just deleting the pfTexture will not free the gl memory.
>
> This is the problem most people run into. I've been told it's not a bug,
> it's a deliberately designed that way because an application may attempt
> to use that handle after a texture is deleted.
>
> I personally think it would be reasonable for Performer to delete this
> handle. It's tricky for an application to delete it otherwise.
>
> Feedback on this design issue would be appreciated.
>
> Cheers,Angus.
>

New Message Reply Date view Thread view Subject view Author view

This archive was generated by hypermail 2.0b2 on Fri Apr 23 1999 - 15:04:38 PDT

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