On 18 May 2011 17:08, Tudor Girba <[email protected]> wrote: > > Hi, > > On 18 May 2011, at 16:51, Levente Uzonyi wrote: > >> On Wed, 18 May 2011, Tudor Girba wrote: >> >>> >>> Hi, >>> >>> On 18 May 2011, at 16:30, Levente Uzonyi wrote: >>> >>>> On Wed, 18 May 2011, Tudor Girba wrote: >>>> >>>>> >>>>> Hi, >>>>> >>>>> Is there a possibility to have any sort of answer on this topic? >>>>> >>>>> It looks to me like this bug is critical given that it prevents us to >>>>> work with images larger than some 200M. >>>> >>>> IMHO it's a problem on the image side. Change the behavior of >>>> #lowSpaceWatcher to fix the problem. >>> >>> How would you do it? :) >> >> According to Igor's mail, the UI process is suspended by the low space >> watcher, which prevents you from seeing the cause of the problem. So, for >> example you could wake up the UI process if that was suspended by the VM >> and/or log some info about the situation. This won't save your image, but >> since it works on non-windows VMs, that's not a problem. > > Thanks for the reply. Unfortunately, I do not know how to do that. > > Furthermore, it's not about one image. These images are produced > automatically several times per day, and people want to be able to download > them and play with the data inside. > > And again, having a 200M image cannot be so unusual. I tried in multiple > situations to simply generate a large enough image and it won't open. > >>> And if it is an image problem, why does it only appear on Windows? >> >> Are you using the same VMs (interpreter/cog, version number matches, etc)? >> If you didn't try so far, then open the image with the latest interpreter VM >> on windows, it has some extra checks for allocations which is not >> implemented in Cog yet. > > I tried with several versions of Cog including the latest ones (on both > platforms) and I got the same result. I did not try with an interpreter VM > because I only have Cog images around (based on Pharo 1.2) and they are not > compatible. >
@Eliot, can you comment or recommend something concerning this issue? > Cheers, > Doru > -- Best regards, Igor Stasenko AKA sig.
