Re: Memory management question

New Message Reply Date view Thread view Subject view Author view

Stephen_Gifford++at++MAPS.CS.CMU.EDU
Fri, 19 Apr 96 16:26:49 -0400

> Is it possible that you have configured a pfMultiprocess mode such as
> PFMP_APP_CULL_DRAW and, at the same time, when you do "Free the old geoset" you
> used pfFree() instead of pfDelete()? If that is the case, you may be
> destroying gsets that pfDraw() would still expect to draw in the next frame
> time, and it gets upset with corrupted memory and dumpts core. PfFree is
> heavy-handed and does not honor the reference counts. You can confirm this is
> true by changing the mode to PFMP_APPCULLDRAW.

        The pfMultiprocess mode has been PFMP_APPCULLDRAW (0) through
all of these attempts. Since we're not actually drawing the geometry,
only using pf functions to manipulate it, pfDraw is never being
called. The program is simply running out of shared memory after
growing larger and larger in a linear fashion.

        This looks to me like a core leak of some kind. I'm curious
if anyone else has had success with similar work: processing 200+MB
of data in a piece by piece fashion (iterating over a rectangular grid
of load modules read in from disk, for example). In particular,
anything where a Performer related core leak would cause a real
problem.

-thanks
 Steve Gifford
 Digital Mapping Laboratory
 School of Computer Science
 Carnegie Mellon University

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:52:45 PDT

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