squeak hogs memory on linux?

James Rupert jrupert at airmail.net
Wed Jun 10 18:51:46 UTC 1998


Try a different video resolution.  I had a problem running out of memory on
a VW image and it turned out to be a problem with the video driver.
Changing to a different video resolution solved the problem.  The problem
being that when the image came up, their was a walkback that tried to
display, which couldn't, which caused a second walkback that tried to
display, ... and so on:-)


James Rupert
jrupert at airmail.net(w)
1 972 226 8883(w)

-----Original Message-----
From: Tim Rowledge <rowledge at interval.com>
To: squeak at cs.uiuc.edu <squeak at cs.uiuc.edu>
Date: Wednesday, June 10, 1998 12:26 PM
Subject: Re: squeak hogs memory on linux?

>On Wed 10 Jun, Greg Lewin wrote:
>> At a vague guess this could be a garbage collection problem.
>> Unfortunately I never have long enough to investigate before the system
>> becomes unusable due to either of the above causes. - at most a minute
>> or two.
>It seems unlikely  to me, since the Object Memory is alloc'd right at the
start of execution and there is no facility for expanding it on the fly; not
that it would be difficult to do.  Garbage collection only operates within
the bounds o
>f object memory and is probably not involved here.
>Perhaps more likely is the small collection of places where some memory is
grabbed for a socket structure, or a buffer for showDisplay and so on. It
seems especially odd since there have been no similar sounding problems
reported for othe
>r unices and the code is pretty much identical.
>Tim Rowledge:  rowledge at interval.com (w)  +1 (650) 856-7230 (w)
> tim at sumeru.stanford.edu (h)  <http://sumeru.stanford.edu/tim>

More information about the Squeak-dev mailing list