phil was working with 3.0 (afaik) mariano was having problems with flushing monticello caches. I think it was not the same. Esteban On Sep 4, 2013, at 5:32 PM, Paul DeBruicker <pdebruic@gmail.com> wrote:
On 09/04/2013 12:54 AM, Esteban Lorenzano wrote:
I'm not sure what we are seeing in pharo3 is the same problem reported in pharo2. Of course if it is, we will backport. But "inflation" problem in ph3 is very consistent and repeatable, the problem reported in ph2... well, I never seen it before, and we have just one report (and I assume that we have more than one hundred production projects with that version). So is likely something different (also some of the detected leaks are due to changes in ph3, not present in the older version).
Esteban
heres two more reports about image size in another thread (Phil & Mariano):
http://forum.world.st/Large-images-reasons-WAS-Re-Pharo-2-0-with-Seaside-DBX...