Image size
Bert Freudenberg
bert at impara.de
Fri Mar 11 16:23:31 UTC 2005
Am 11.03.2005 um 13:04 schrieb Tobias Germer:
> Scott Wallace wrote:
>> Looking at a space analysis might lead you quickly to discover which
>> kinds of objects are suddenly taking up so much space. Armed with
>> that, it might then be obvious what's going on, but if not, if you
>> shared that space analysis with the mailing list you might get some
>> help pretty quickly.
>> To print a space analysis, evaluate "SpaceTally new
>> printSpaceAnalysis", then look at the disk file "STSpace.text" that
>> will be produced by the analysis. Pay special attention to the final
>> two columns, where space for each class's instances, and percentage
>> of total space used (if above .1%) are listed.
>
> Verrrry interesting! The majority of space is assigned to arrays. The
> entries with >=3.0% of space are:
>
> ByteArray 66.3%
> B3DVector3Array 6.5%
> IntegerArray 3.4%
> Array 3.0%
>
> So ByteArray seems to be the bad guy. So what can I do next? Can I
> collect the zombie arrays or anything?
If something does not go away after a full garbage collect, then it is
still referenced by something else. Here are some things you might try:
http://minnow.cc.gatech.edu/squeak/2631
- Bert -
More information about the Squeak-dev
mailing list
|