As I have discovered recently I quite regularly have large images (500+
MB); the reason seems to be combination of memory leaks, Roassal (maybe
Athens), GUI, and a LOT of saving while having all those things opened. But
Image cleanup tends to shrink it back to tens of megabytes.
Personally I don't
Nice!
On Wed, May 13, 2015 at 8:51 AM, Sean P. DeNigris
wrote:
> laura wrote
> > Also the discussion brought up very interesting msg collaborations
> > snippets
> > and system features for future reference!
>
> I compiled them at
> https://github.com/pharo-project/pharo-core/wiki/Memory-Hogs
>
>
laura wrote
> Also the discussion brought up very interesting msg collaborations
> snippets
> and system features for future reference!
I compiled them at
https://github.com/pharo-project/pharo-core/wiki/Memory-Hogs
-
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Imag
nders via Pharo-users" <
pharo-users@lists.pharo.org> a écrit :
>
>
> -- Forwarded message --
> From: Cameron Sanders
> To: Any question about pharo is welcome
> Cc:
> Date: Tue, 3 Feb 2015 23:11:12 -0500
> Subject: Re: [Pharo-users] Image g
> On 07 Feb 2015, at 17:43, Laura Risani wrote:
>
> Problemution (problem+solution) found!
>
> I've tried
> clearing package cache, image cleanup -> size decreased a little.
> unloading all my packages -> size unchanged.
>
> Yet i haven't thought as my doing about TilingWindowManager i've in
Problemution (problem+solution) found!
I've tried
clearing package cache, image cleanup -> size decreased a little.
unloading all my packages -> size unchanged.
Yet i haven't thought as my doing about TilingWindowManager i've installed!
It has an option for snapshooting worlds, it's possible i'v
> On 07 Feb 2015, at 10:19, Thierry Goubier wrote:
>
> Hi,
>
> a fairly long report on the image and memory hogs is :
>
> SmalltalkImage current reportCPUandRAM
Cool. I didn't know that one. Thanks.
> Writes files in the image folder containing all the information. Takes a
> while to run.
>
I had this trouble with Squeak. It transpired that Squeak has a recycle
bin! I changed a preference and all my junk objects disappeared.
On 07.02.2015 10:19, Thierry Goubier wrote:
Hi,
a fairly long report on the image and memory hogs is :
SmalltalkImage current reportCPUandRAM
Writes files
Hi,
a fairly long report on the image and memory hogs is :
SmalltalkImage current reportCPUandRAM
Writes files in the image folder containing all the information. Takes a
while to run.
Thierry
2015-02-07 9:53 GMT+01:00 Stephan Eggermont :
> You might want to inspect this to see if this gets y
You might want to inspect this to see if this gets you something
interesting.
(Object allSubclasses collect: [ :aClass |
aClass -> aClass allInstances size])
sort: [ :a :b | a value > b value ]
It takes some time to run, especially in a larger image.
Stephan
Personally I never got a 200MB image size, you have very likely
persisted large collection of objects of your own in your image.
Le 06/02/2015 23:29, Laura Risani a écrit :
> I've tried, at some degree, all of your suggestions, but i failed to
> reduce the image size significantly. I'll keep tryin
I've tried, at some degree, all of your suggestions, but i failed to reduce
the image size significantly. I'll keep trying, meantime i've started with
a fresh image.
Thank you for your answers.
Best,
Laura
On Wed, Feb 4, 2015 at 11:10 AM, Hilaire wrote:
> Le 03/02/2015 17:49, Laura Risani a écr
Le 03/02/2015 17:49, Laura Risani a écrit :
> The official image i've downloaded weighted about 40 MB. Now its size
> is about 200 MB. What is the explanation? Is this normal or have i
> done something wrong?
>
You may want to try World menu>System>Do image clean up
Hilaire
--
Dr. Geo - http://d
On Wed, Feb 4, 2015 at 12:49 AM, Laura Risani
wrote:
> Hi all,
>
> The official image i've downloaded weighted about 40 MB. Now its size is
> about 200 MB. What is the explanation? Is this normal or have i done
> something wrong?
>
> I haven't been using globals, just downloaded and defined some
Hello,
There could be many reasons why you would have such a big image.
The most common reason is the monticello metadata, as Phil said.
Another reason could be because some caches and objects that are flushed on
snapshot, so if you looked at the image size at runtime and not the file
size (for
--- Begin Message ---
Do any of your (class/pool variable) singleton instances store data? add a
#clearAll or #reset (mySingletonVar := nil) to the class side -- or
whatever fits your app -- and do that before that #garbageCollect block.
[In fact, put that in some XXXAdmin class]
Good Luck,
Cam
O
Try to open monticello and select any repo, right click and clear the
package cache.
If you are using monticello that is.
Also close all windows, open a workspace and do the
10 timesRepeat: [ Smalltalk garbageCollect].
HTH
Phil
Le 3 févr. 2015 17:49, "Laura Risani" a écrit :
> Hi all,
>
> Th
Hi all,
The official image i've downloaded weighted about 40 MB. Now its size is
about 200 MB. What is the explanation? Is this normal or have i done
something wrong?
I haven't been using globals, just downloaded and defined some packages.
The only over persistent thing i've done is to keep an in
18 matches
Mail list logo
