| From: | |
| Date: | 13 Feb 2001 at 16:13:20 |
| Subject: | Re: chip memory defragmentation |
It sounds like you're leaving little bits behind & not
de-allocating it, leaving the memory segmented.
Try using AllocVec() instead of AllocMem(),
that way, you free exactly the amount you allocated
without you having to keep track of the size..
FreeVec() only required the memory address parameter...
On 14-Feb-01, William Robinson wrote:
> GRRR!!
> ok, it's me again.
> thanks for all the help so far.
> i have installed MuGuardianAngel and SegTracker (& MuForce, of
> course), after trying enforcer and not liking the aftertaste it left.
> so, i run my program for the first time (remember, the simple double
> buffer one) and it's all fine, the little graphical memory watcher
> thing that comes with poolmem looks ok, avail in shell says i have
> plenty of memory left. everything is fine after it... maybe i have a
> little less chip RAM than before, but i can live with that. no
> MuGuardianAngel hits. then i run it for the second time and my chip
> ram gets totally defragmente; avail and the workbench bar say that i
> have about 1600k left, but the largest chunk is about 30/40k!
> Are there any known bugs with this kindof thing?
> much obliged, as always.
> bill
Regards
Colin Wenzel. Quensland, Australia.
EMAIL: colstv@hotkey.net.au
URL: http://www.hotkey.net.au/~colstv/
AMIGA: 4000T, 68060/50, 150Mb RAM,
OS 3.9, Spectrum Gfx Card + P96.
Need an Image Generator For CATV ??
http://connect.to/products
_________________________________________
------------------------ Yahoo! Groups Sponsor ---------------------~-~>
eGroups is now Yahoo! Groups
Click here for more details
http://click.egroups.com/1/11231/0/_/451227/_/982077242/
---------------------------------------------------------------------_->