Re: pw->open()/closeGL() with PFMP_APPCULLDRAW

New Message Reply Date view Thread view Subject view Author view

Sharon Clay (src++at++rose.engr.sgi.com)
Fri, 30 Jan 1998 01:26:05 -0800

+>---- On Jan 29, 4:22pm, Masahiko Yamanaka wrote:
> Subject: pw->open()/closeGL() with PFMP_APPCULLDRAW
->
->Hello all,
->
->When I call pw->open()/closeGL() many times with PFMP_APPCULLDRAW mode
->memory leaking seems to occur... and No problem with PFMP_APPCULL_DRAW.
->
->I changed simple.C as followings, and created simple.ogldso.
->
-> pfMultiprocess( PFMP_DEFAULT ); ---> pfMultiprocess( PFMP_APPCULLDRAW );
-> pw->open() ---> while(1){ pw->open(); pw->closeGL(); }
->
->As looking at gmemusage, the ratio of simple.ogldso rises...
->
->I tested with Perf2.0.2(dev)&Perf2.0.3(eoe)/O2
-> & Perf2.0.2(dev)&Perf2.0.4(eoe)/OCTANE.
->
->I'm getting Perf2.2 however not yet.
->Could anyone tell me whether this phenomenon disappears with Perf2.2?
->

The Performer part of this leak should be fixed in 2.2.
The IMPACT GL also used to leak if you had created textures in the
gfx context. Also, it should have still beeen leaking in
PFMP_APPCULL_DRAW mode. If you are MP, the Performer part
will be allocated out of the heap and in both process models the
GL part is allocated off the heap.

src.

-- 
-----{-----{---++at++   -----{----{---++at++   -----{----{---++at++   -----{----{---++at++
Sharon Rose Clay - Silicon Graphics, Advanced Systems Dev.
src++at++sgi.com  (650) 933 - 1002  FAX: (650) 965 - 2658  MS 8U-590
-----{-----{---++at++   -----{----{---++at++   -----{----{---++at++   -----{----{---++at++
=======================================================================
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:39 PDT

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