Re: Performer crash
John Rohlf (jrohlf++at++tubes)
Fri, 30 Jun 95 15:37:16 PDT
>
>
> Using performer 1.2 on a Crimson RE, problems arise associating with
> pfDelete (as far as I can tell, this is the cause). I would appreciate
> any suggestions on a solution.
> I have an on-line terrain generation routine, which upon operator request
> will be discarded and / or modified. I discard old nodes which are no
> longer needed. However, as soon as I discard old nodes (pfDelete) and
> load new ones, a segmet violation occurs. The draw routine (pfApplyTex)
> no longer finds texture associated with the geostates. Discarding alone
> causes no problems.
> Does pfDelete also delete the texture reference and/or delete the texture?
> Does pfDelete also delete the geostate (assuming refcount =0)?
>
> I tried making new states and , re-downloading all textures upon
> regenerating terrain, but Performer still crashes with the same error.
>
> Any ideas as to the cause is appreciated.
>
pfDelete follows the reference chain, pfUnrefDelete'ing as it goes
until it encounters an object with > 0 reference count. So the answer
to your question is yes, pfDelete will delete the pfGeoState and
the pfTexture if their ref counts reach 0. If you want to reuse
any objects, call pfRef(object) to increment its reference count.
This archive was generated by hypermail 2.0b2
on Mon Aug 10 1998 - 17:51:37 PDT