Xref: utzoo comp.sys.mac.system:7631 comp.sys.mac.programmer:26245 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!spool.mu.edu!cs.umn.edu!ux.acs.umn.edu!oleary From: oleary@ux.acs.umn.edu (Doc O'Leary) Newsgroups: comp.sys.mac.system,comp.sys.mac.programmer Subject: Re: Memory wall Message-ID: <4182@ux.acs.umn.edu> Date: 21 Jun 91 23:00:10 GMT References: <1991Jun21.204929.10138@ux1.cso.uiuc.edu> Followup-To: comp.sys.mac.system Organization: University of Minnesota, Academic Computing Services Lines: 27 In article <1991Jun21.204929.10138@ux1.cso.uiuc.edu> resnick@cogsci.uiuc.edu (Pete Resnick) writes, among other things: >I seem to sometimes get a small wall in my memory. When going into the >About this Macintosh window, sometimes the memory is fragmented (as >evidenced by the largest available block being much smaller than what >is left when you add up everything in the box), but I am only running >Finder. It looks like someone is leaving a block of memory stuck >somewhere in the middle of my free space and it is not getting >released. But it can't be an application, since there are none running, >and when an app exits, it takes it's heap with it. So where is this >wall coming from? I have Macsbug, so if someone tells me what to look >for, I will be perfectly willing to walk through all 4 Meg looking for >this silly thing. My bet is that it was the system that caused the fragmentation. One of the times, it expanded its heap while you were running applications and fragmented the memory that would be available after the applications were quit. --------- Doc ********************** Signature Block : Version 2.6 ********************* * | * * "Was it love, or was it the idea | It's hard to look cool with your * * of being in love?" -- PF | arm Super-Glued to your forehead * * (BTW, which one *is* Pink?) | * * | --->oleary@ux.acs.umn.edu<--- * ****************** Copyright (c) 1991 by Doc O'Leary ********************