[Pharo-project] cogwin/Croquet (Win7) + Moose + very large models = crash (out of Memory)

[Hani Abdeen]

Hello,

I'm using cogwin/Croquet VM (last version http://www.mirandabanda.org/files/Cog/VM/VM.r2522/) on windows7, 

and today I had this probelm: when the size of the pharo image become so large the VM crashes with reason 'out of memory'. 

The same problem with previous versions of cogwin.

Note that I use a PC with 8G of RAM, so it's really damage to have such a problem.

Any idea about another VM working well on Windows and does not have such an issues?

Any urgent solution?

Thanks,

Hani

[Paul DeBruicker]

Hani Abdeen wrote

From this thread:
http://forum.world.st/experience-with-large-images-td4101765.html

It seems that on windows the size of the image by default is limited to
500MB in RAM. I don't know if you can change it or not. Linux/Mac is
limited to 2GB. Can you try your experiments on a Mac?

--
View this message in context: http://forum.world.st/cogwin-Croquet-Win7-Moose-very-large-models-crash-out-of-Memory-tp4328688p4328761.html
Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

[Hani Abdeen]

On 25 January 2012 23:05, Paul DeBruicker <pdeb...@gmail.com> wrote:

Hani Abdeen wrote

>
> Hello,
>
> I'm using cogwin/Croquet VM (last version
> http://www.mirandabanda.org/files/Cog/VM/VM.r2522/) on windows7,
> and today I had this probelm: when the size of the pharo image become so
> large the VM crashes with reason 'out of memory'.
> The same problem with previous versions of cogwin.
> Note that I use a PC with 8G of RAM, so it's really damage to have such a
> problem.
>
> Any idea about another VM working well on Windows and does not have such
> an
> issues?
> Any urgent solution?
>
> Thanks,
> Hani
>

From this thread:
http://forum.world.st/experience-with-large-images-td4101765.html

It seems that on windows the size of the image by default is limited to
500MB in RAM.  I don't know if you can change it or not.  Linux/Mac is
limited to 2GB.  Can you try your experiments on a Mac?

Unfortunately no, I've not Mac, and the company for which I'll use Moose on their software, Tomorrow morning :(, do not use Mac.

[Hani Abdeen]

Hi,

[Mariano Martinez Peck]

I think Igor fixed that for the Windows VM, but such changes were not integerated in Eliot VMs, but rather in the branch of Git.
But since the Jenkins is not building Windows VM, I have no idea where you can get such a VM.

Cheers

--
Mariano
http://marianopeck.wordpress.com

[Paul DeBruicker]

Hani Abdeen wrote
>
> On 25 January 2012 23:05, Paul DeBruicker &lt;pdebruic@&gt; wrote:
>
>>
>> Hani Abdeen wrote

>> >
>>
>> It seems that on windows the size of the image by default is limited to
>> 500MB in RAM. I don't know if you can change it or not. Linux/Mac is
>> limited to 2GB. Can you try your experiments on a Mac?
>>
>
> Unfortunately no, I've not Mac, and the company for which I'll use Moose
> on
> their software, Tomorrow morning :(, do not use Mac.
>
>>
>

Can you run virtualbox on your windows machine? I have a 32 bit debian
linux (vers 6.0.3) virtual disk image (2.5GB RAM, 8GB disk) you coudl use
that would let you hit the limit of what Pharo 32 bit can work with.

--
View this message in context: http://forum.world.st/cogwin-Croquet-Win7-Moose-very-large-models-crash-out-of-Memory-tp4328688p4329088.html

[Stéphane Ducasse]

why jenkins is not building the vm windows?

Stef

[Stéphane Ducasse]

Hani

first import less information for your demo. You probably do not need this and local argument.

stef

[Hani Abdeen]

Hi Stef,

On 26 January 2012 10:05, Stéphane Ducasse <stephane...@inria.fr> wrote:

Hani

first import less information for your demo. You probably do not need this and local argument.

yes I think so, 

I've also a pre loaded demo java model to demonstrate it

Guillermo told me that he just compiled a VM for windows and he can send it to me to try. may be he did not read my email yet.

I'll also see if they have a Linux machine on which we can on the image usign Pharo VM.

Thanks

Hani

[Igor Stasenko]

On 25 January 2012 23:18, Mariano Martinez Peck <maria...@gmail.com> wrote:
> I think Igor fixed that for the Windows VM, but such changes were not
> integerated in Eliot VMs, but rather in the branch of Git.
> But since the Jenkins is not building Windows VM, I have no idea where you
> can get such a VM.
>

No, changes are there. But they are not "fixing" the hard limit which
is still 512M.
They only fixing a strange issue with growing image close to that
limit (so 400M (and even less size) images was crashing before even
reaching a limit).
This is because of miscalculation between requested space and
available space, after memory growth.

--
Best regards,
Igor Stasenko.