Article View: comp.graphics.explorer
Article #62Reference counts
From: Drought Research Account
Date: Wed, 29 Jul 1992 03:37
Date: Wed, 29 Jul 1992 03:37
19 lines
1259 bytes
1259 bytes
I have written a module which creates a lattice, using cxLatNew. The module is actually to read in an obscure data format, so it needs to read the file first to know how big to create the lattice. This is why I can't just let the module data wrapper create the lattice for me. The question is, if I am reading many files using this, i.e. the module is firing over and over again, I am coninually creating lattices and never free-ing them. Even if all downstream modules manage to decrement their reference counts correctly, on receipt of the next lattice, there does not seem to be any way thet my module can decrement the reference count to the previously created lattice, before creating a new one. What does actually happen is that I slowly fill up more and more of the shared memory arena. What am I supposed to be doing in this situation ? Any hints ? thanks in advance Neil Flood
Technical Details
Message-ID:
<1992Jul29.033720.28549@qdpii.comp.qdpi.oz.au>Path:
arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!bunyip.cc.uq.oz.au!qdpii!dresShow Full Headers
Complete Article Headers
Newsgroups: comp.graphics.explorer Path: arc1-ca.pugleaf.net!sparky!uunet!munnari.oz.au!bunyip.cc.uq.oz.au!qdpii!dres From: dres@qdpii.comp.qdpi.oz.au (Drought Research Account) Subject: Reference counts Message-ID: <1992Jul29.033720.28549@qdpii.comp.qdpi.oz.au> Organization: Queensland Dept Primary Industries. Date: Wed, 29 Jul 1992 03:37:20 GMT Lines: 20