thanks paul for the information.
We should pay attention to this.
May be we will have to have one release of Pharo focusing on not improving the
libraries but
its runtime behavior.
The problem is that we need enough room to move and improve the infrastructure.
> I've been developing in the sam
On Jul 18, 2013, at 8:04 AM, Marcus Denker wrote:
>
> On Jul 17, 2013, at 9:59 PM, Paul DeBruicker wrote:
>
>> I've been developing in the same Pharo2 image for a couple weeks and its
>> now 180MB. I use the same development habits as in Pharo 1.4 but there
>> the image would only be about 4
On Jul 17, 2013, at 9:59 PM, Paul DeBruicker wrote:
> I've been developing in the same Pharo2 image for a couple weeks and its
> now 180MB. I use the same development habits as in Pharo 1.4 but there
> the image would only be about 40MB.
>
I already saw that the current 3.0 download has 110.0
Did you check on Dictionaries / Sets (+ their Identity* versions) and Symbols
as well?
Another possibility would non terminated Processes (process browser)?
The Arrays themselves already look suspicious.
Usually the way to track such objects down is to find and interesting candidate
and inspec
I've been developing in the same Pharo2 image for a couple weeks and its
now 180MB. I use the same development habits as in Pharo 1.4 but there
the image would only be about 40MB.
Using SpaceTally I can see that I have 40 MB of Arrays. And 10MB of
Bitmaps. 8MB of Floats, Strings, & OrderedCollect
