From: Hani Abdeen <hani....@gmail.com>Subject: [Moose-dev] Re: cogwin/Croquet (Win7) + Moose + very large model = crash (out of Memory)Date: January 26, 2012 8:52:15 AM GMT+01:00To: Moose-related development <moos...@iam.unibe.ch>Reply-To: Moose-related development <moos...@iam.unibe.ch>
Hi Doru,the image size starts at 400M, before doing anything on the model.Now, as I start manipulating the model and sending navigation queries, trying to create an Arki report about the model, the image size apparently exceed 500M and the VM crashes!For more information I enclosed the header of the crash.dmp file.Cheers,Hani---------------------------------------------------------------------Fri Jan 13 14:57:11 2012Error in the VM threadReason: out of memoryHardware information:Manufacturer: UnknownModel: UnknownNumber of processors: 4Page size: 4096Memory Information (upon launch):Physical Memory Size: 4194303 kbytesPhysical Memory Free: 4194303 kbytesPage File Size: 4194303 kbytesPage File Free: 4194303 kbytesVirtual Memory Size: 2097024 kbytesVirtual Memory Free: 2025868 kbytesMemory Load: 20 percentProcessor 0: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHzIdentifier: Intel64 Family 6 Model 42 Stepping 7~MHZ: 2494Processor 1: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHzIdentifier: Intel64 Family 6 Model 42 Stepping 7~MHZ: 2494Processor 2: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHzIdentifier: Intel64 Family 6 Model 42 Stepping 7~MHZ: 2494Processor 3: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHzIdentifier: Intel64 Family 6 Model 42 Stepping 7~MHZ: 2494Operating System: Windows 7 Ultimate (Build 7600 )Registered Owner: MicrosoftRegistered Company: MicrosoftSP major version: 0SP minor version: 0Suite mask: 100Product type: 1Display Information:Graphics adapter name: Intel(R) HD Graphics FamilyPrimary monitor resolution: 1366 x 768Device: RDPDD Chained DDAdapter String: ???Bios String: ???Chip Type: ???DAC Type: ???Memory Size: 0xFFFFFFFFDriver Versions:RDPDD:VM Version: Cog VM 4.0.0 (release) from Dec 1 2011Compiler: gcc 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)Interpreter Build: CoInterpreter VMMaker.oscog-eem.138 uuid: f9a63bdf-7bbc-4ae5-9634-ecd6fd814c9d Dec 1 2011Cogit Build: StackToRegisterMappingCogit VMMaker.oscog-eem.139 uuid: c2849383-9768-4948-b9b2-a5c22d482b07 Dec 1 2011_______________________________________________On 26 January 2012 07:29, Tudor Girba <tu...@tudorgirba.com> wrote:
Hi,
What does large mean in your case? I routinely work with 500MB images on Windows 7 using the same VM.
Cheers,
Doru
> _______________________________________________
On 25 Jan 2012, at 23:25, 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.
> I've only one, but very large, Java model in Moose.
> 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?
>
> Unfortunately I've not Mac and the company for which I'am going to demonstrate Moose, on their code base and Tomorrow morning do not use Mac.
>
> Thanks,
> Hani
> Moose-dev mailing list
> Moos...@iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"What is more important: To be happy, or to make happy?"
_______________________________________________
Moose-dev mailing list
Moos...@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list
Moos...@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
521M is a hard limit for windows 32bit VM, sorry.
I think that it would be better for you to check 64bit version of vm..
or, as i suggested already, change your data model(s) and introduce
cache, or other memory conservation schemes.
--
Best regards,
Igor Stasenko.
Cog works on 32bit only for now.