out of memory - cog on windows

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
48 messages Options
123
Reply | Threaded
Open this post in threaded view
|

out of memory - cog on windows

Tudor Girba
Hi,

I received a question from someone running a 200MB image on Windows using Cog 2361.

If I open the image on Mac, it works just fine. Unfortunately, I do not have a Windows machine around, and I cannot test but I believe it should be solvable by increasing the allocated memory.

On Mac, I would run it with: ./Croquet -memory 1500m

Can anyone help me with the right incantation for Windows?

Cheers,
Doru


--
www.tudorgirba.com

"What we can governs what we wish."




Space is low.png (15K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Mariano Martinez Peck


On Thu, Apr 21, 2011 at 12:52 PM, Tudor Girba <[hidden email]> wrote:
Hi,

I received a question from someone running a 200MB image on Windows using Cog 2361.

If I open the image on Mac, it works just fine. Unfortunately, I do not have a Windows machine around, and I cannot test but I believe it should be solvable by increasing the allocated memory.

On Mac, I would run it with: ./Croquet -memory 1500m


You should be able to do the same in Windows. But, I think (I may be wrong) that the windows VM doesn't support more than 512MB. Maybe with Cog that is not true anymore.
I don't know.
 
Can anyone help me with the right incantation for Windows?

Cheers,
Doru


--
www.tudorgirba.com

"What we can governs what we wish."






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

Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Tudor Girba
In reply to this post by Tudor Girba
> Hi again,
>
> I did not say what the problem was :). The problem was that when opening the image on Windows, he got a Space is low message and the image was not usable (see attachment). On Mac it worked just fine.
>
> Cheers,
> Doru
>
>

>

>
>
> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>
>> Hi,
>>
>> I received a question from someone running a 200MB image on Windows using Cog 2361.
>>
>> If I open the image on Mac, it works just fine. Unfortunately, I do not have a Windows machine around, and I cannot test but I believe it should be solvable by increasing the allocated memory.
>>
>> On Mac, I would run it with: ./Croquet -memory 1500m
>>
>> Can anyone help me with the right incantation for Windows?
>>
>> Cheers,
>> Doru
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "What we can governs what we wish."
>>
>>
>>
>> <Space is low.png>
>
> --
> www.tudorgirba.com
>
> "Yesterday is a fact.
> Tomorrow is a possibility.
> Today is a challenge."
>
>
>

Space is low.png (15K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Mariano Martinez Peck


On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba <[hidden email]> wrote:
> Hi again,
>
> I did not say what the problem was :). The problem was that when opening the image on Windows, he got a Space is low message and the image was not usable (see attachment).

That's weird. Does moose have something on the startup list?   something that can be bothering there?

 
On Mac it worked just fine.
>
> Cheers,
> Doru
>
>

>
>
>
> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>
>> Hi,
>>
>> I received a question from someone running a 200MB image on Windows using Cog 2361.
>>
>> If I open the image on Mac, it works just fine. Unfortunately, I do not have a Windows machine around, and I cannot test but I believe it should be solvable by increasing the allocated memory.
>>
>> On Mac, I would run it with: ./Croquet -memory 1500m
>>
>> Can anyone help me with the right incantation for Windows?
>>
>> Cheers,
>> Doru
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "What we can governs what we wish."
>>
>>
>>
>> <Space is low.png>
>
> --
> www.tudorgirba.com
>
> "Yesterday is a fact.
> Tomorrow is a possibility.
> Today is a challenge."
>
>
>




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

Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Tudor Girba
Hi,



On Apr 21, 2011, at 14:06, Mariano Martinez Peck <[hidden email]> wrote:



On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba <[hidden email]> wrote:
> Hi again,
>
> I did not say what the problem was :). The problem was that when opening the image on Windows, he got a Space is low message and the image was not usable (see attachment).

That's weird. Does moose have something on the startup list?   something that can be bothering there?

Not that I know of. Is there a way to check this?

Actually, using exactly the same process some days ago he produced an image of 190MB. This one works just fine on Windows. The only difference between the two is the size of the loaded data.

It would be really bad news if the Windows vm would be so severely limited in terms of memory.

Cheers,
Doru


 
On Mac it worked just fine.
>
> Cheers,
> Doru
>
>

>
>
>
> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>
>> Hi,
>>
>> I received a question from someone running a 200MB image on Windows using Cog 2361.
>>
>> If I open the image on Mac, it works just fine. Unfortunately, I do not have a Windows machine around, and I cannot test but I believe it should be solvable by increasing the allocated memory.
>>
>> On Mac, I would run it with: ./Croquet -memory 1500m
>>
>> Can anyone help me with the right incantation for Windows?
>>
>> Cheers,
>> Doru
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "What we can governs what we wish."
>>
>>
>>
>> <Space is low.png>
>
> --
> www.tudorgirba.com
>
> "Yesterday is a fact.
> Tomorrow is a possibility.
> Today is a challenge."
>
>
>




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

Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Luc Fabresse
Hi Doru,

2011/4/21 Tudor Girba <[hidden email]>
Hi,



On Apr 21, 2011, at 14:06, Mariano Martinez Peck <[hidden email]> wrote:



On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba <[hidden email][hidden email]> wrote:
> Hi again,
>
> I did not say what the problem was :). The problem was that when opening the image on Windows, he got a Space is low message and the image was not usable (see attachment).

That's weird. Does moose have something on the startup list?   something that can be bothering there?

Not that I know of. Is there a way to check this?

Classes should be registered using Smalltlak addToStartUpList: aClass
Then aClass class>>#startUp: is executed at startup.
So implementors of #startUp: on Moose classes should give you the answer.

#Luc


Actually, using exactly the same process some days ago he produced an image of 190MB. This one works just fine on Windows. The only difference between the two is the size of the loaded data.

It would be really bad news if the Windows vm would be so severely limited in terms of memory.

Cheers,
Doru


 
On Mac it worked just fine.
>
> Cheers,
> Doru
>
>

>
>
>
> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>
>> Hi,
>>
>> I received a question from someone running a 200MB image on Windows using Cog 2361.
>>
>> If I open the image on Mac, it works just fine. Unfortunately, I do not have a Windows machine around, and I cannot test but I believe it should be solvable by increasing the allocated memory.
>>
>> On Mac, I would run it with: ./Croquet -memory 1500m
>>
>> Can anyone help me with the right incantation for Windows?
>>
>> Cheers,
>> Doru
>>
>>
>> --
>> www.tudorgirba.com
>>
>> "What we can governs what we wish."
>>
>>
>>
>> <Space is low.png>
>
> --
> www.tudorgirba.com
>
> "Yesterday is a fact.
> Tomorrow is a possibility.
> Today is a challenge."
>
>
>




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


Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Tudor Girba
Hi,

We have no specific startUp: methods in Moose. In any case, the issue with opening the image does not seem to be related to startUp:.

Is it really true that the Cog VM is limited to 512MB of memory?

Cheers,
Doru


On 21 Apr 2011, at 14:27, Luc Fabresse wrote:

> Hi Doru,
>
> 2011/4/21 Tudor Girba <[hidden email]>
> Hi,
>
>
>
> On Apr 21, 2011, at 14:06, Mariano Martinez Peck <[hidden email]> wrote:
>
>>
>>
>> On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba <[hidden email]> wrote:
>> > Hi again,
>> >
>> > I did not say what the problem was :). The problem was that when opening the image on Windows, he got a Space is low message and the image was not usable (see attachment).
>>
>> That's weird. Does moose have something on the startup list?   something that can be bothering there?
>
> Not that I know of. Is there a way to check this?
>
> Classes should be registered using Smalltlak addToStartUpList: aClass
> Then aClass class>>#startUp: is executed at startup.
> So implementors of #startUp: on Moose classes should give you the answer.
>
> #Luc
>
>
> Actually, using exactly the same process some days ago he produced an image of 190MB. This one works just fine on Windows. The only difference between the two is the size of the loaded data.
>
> It would be really bad news if the Windows vm would be so severely limited in terms of memory.
>
> Cheers,
> Doru
>
>
>>  
>> On Mac it worked just fine.
>> >
>> > Cheers,
>> > Doru
>> >
>> >
>>
>> >
>> >
>> >
>> > On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>> >
>> >> Hi,
>> >>
>> >> I received a question from someone running a 200MB image on Windows using Cog 2361.
>> >>
>> >> If I open the image on Mac, it works just fine. Unfortunately, I do not have a Windows machine around, and I cannot test but I believe it should be solvable by increasing the allocated memory.
>> >>
>> >> On Mac, I would run it with: ./Croquet -memory 1500m
>> >>
>> >> Can anyone help me with the right incantation for Windows?
>> >>
>> >> Cheers,
>> >> Doru
>> >>
>> >>
>> >> --
>> >> www.tudorgirba.com
>> >>
>> >> "What we can governs what we wish."
>> >>
>> >>
>> >>
>> >> <Space is low.png>
>> >
>> > --
>> > www.tudorgirba.com
>> >
>> > "Yesterday is a fact.
>> > Tomorrow is a possibility.
>> > Today is a challenge."
>> >
>> >
>> >
>>
>>
>>
>>
>> --
>> Mariano
>> http://marianopeck.wordpress.com
>>
>

--
www.tudorgirba.com

"Beauty is where we see it."




Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Alain rastoul
Hi Tudor,

There is a constant in sqWin32Alloc.h (platforms\win32\vm) :
#define MAX_VIRTUAL_MEMORY 512*1024*1024
you can change it to whatever you want and rebuild the vm,
for exzmple give all the available memory less 256 M .

HTH

Regards
Alain

"Tudor Girba" <[hidden email]> a écrit
dans le message de news: [hidden email]...
Hi,

We have no specific startUp: methods in Moose. In any case, the issue with
opening the image does not seem to be related to startUp:.

Is it really true that the Cog VM is limited to 512MB of memory?

Cheers,
Doru


On 21 Apr 2011, at 14:27, Luc Fabresse wrote:

> Hi Doru,
>
> 2011/4/21 Tudor Girba
> <[hidden email]>
> Hi,
>
>
>
> On Apr 21, 2011, at 14:06, Mariano Martinez Peck
> <[hidden email]> wrote:
>
>>
>>
>> On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba
>> <[hidden email]> wrote:
>> > Hi again,
>> >
>> > I did not say what the problem was :). The problem was that when
>> > opening the image on Windows, he got a Space is low message and the
>> > image was not usable (see attachment).
>>
>> That's weird. Does moose have something on the startup list?   something
>> that can be bothering there?
>
> Not that I know of. Is there a way to check this?
>
> Classes should be registered using Smalltlak addToStartUpList: aClass
> Then aClass class>>#startUp: is executed at startup.
> So implementors of #startUp: on Moose classes should give you the answer.
>
> #Luc
>
>
> Actually, using exactly the same process some days ago he produced an
> image of 190MB. This one works just fine on Windows. The only difference
> between the two is the size of the loaded data.
>
> It would be really bad news if the Windows vm would be so severely limited
> in terms of memory.
>
> Cheers,
> Doru
>
>
>>
>> On Mac it worked just fine.
>> >
>> > Cheers,
>> > Doru
>> >
>> >
>>
>> >
>> >
>> >
>> > On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>> >
>> >> Hi,
>> >>
>> >> I received a question from someone running a 200MB image on Windows
>> >> using Cog 2361.
>> >>
>> >> If I open the image on Mac, it works just fine. Unfortunately, I do
>> >> not have a Windows machine around, and I cannot test but I believe it
>> >> should be solvable by increasing the allocated memory.
>> >>
>> >> On Mac, I would run it with: ./Croquet -memory 1500m
>> >>
>> >> Can anyone help me with the right incantation for Windows?
>> >>
>> >> Cheers,
>> >> Doru
>> >>
>> >>
>> >> --
>> >> www.tudorgirba.com
>> >>
>> >> "What we can governs what we wish."
>> >>
>> >>
>> >>
>> >> <Space is low.png>
>> >
>> > --
>> > www.tudorgirba.com
>> >
>> > "Yesterday is a fact.
>> > Tomorrow is a possibility.
>> > Today is a challenge."
>> >
>> >
>> >
>>
>>
>>
>>
>> --
>> Mariano
>> http://marianopeck.wordpress.com
>>
>

--
www.tudorgirba.com

"Beauty is where we see it."








Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Tudor Girba
Hi,

Should I to understand that the only way to enable more memory is to recompile the VM? Does that mean that there is no way to pass this information as a parameter like we can on Mac?

The problem is that I cannot recompile the VM because I have no access to a Windows machine. Is there one available that provides more memory?

Cheers,
Doru


On 21 Apr 2011, at 22:09, Alain_Rastoul wrote:

> Hi Tudor,
>
> There is a constant in sqWin32Alloc.h (platforms\win32\vm) :
> #define MAX_VIRTUAL_MEMORY 512*1024*1024
> you can change it to whatever you want and rebuild the vm,
> for exzmple give all the available memory less 256 M .
>
> HTH
>
> Regards
> Alain
>
> "Tudor Girba" <[hidden email]> a écrit
> dans le message de news: [hidden email]...
> Hi,
>
> We have no specific startUp: methods in Moose. In any case, the issue with
> opening the image does not seem to be related to startUp:.
>
> Is it really true that the Cog VM is limited to 512MB of memory?
>
> Cheers,
> Doru
>
>
> On 21 Apr 2011, at 14:27, Luc Fabresse wrote:
>
>> Hi Doru,
>>
>> 2011/4/21 Tudor Girba
>> <[hidden email]>
>> Hi,
>>
>>
>>
>> On Apr 21, 2011, at 14:06, Mariano Martinez Peck
>> <[hidden email]> wrote:
>>
>>>
>>>
>>> On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba
>>> <[hidden email]> wrote:
>>>> Hi again,
>>>>
>>>> I did not say what the problem was :). The problem was that when
>>>> opening the image on Windows, he got a Space is low message and the
>>>> image was not usable (see attachment).
>>>
>>> That's weird. Does moose have something on the startup list?   something
>>> that can be bothering there?
>>
>> Not that I know of. Is there a way to check this?
>>
>> Classes should be registered using Smalltlak addToStartUpList: aClass
>> Then aClass class>>#startUp: is executed at startup.
>> So implementors of #startUp: on Moose classes should give you the answer.
>>
>> #Luc
>>
>>
>> Actually, using exactly the same process some days ago he produced an
>> image of 190MB. This one works just fine on Windows. The only difference
>> between the two is the size of the loaded data.
>>
>> It would be really bad news if the Windows vm would be so severely limited
>> in terms of memory.
>>
>> Cheers,
>> Doru
>>
>>
>>>
>>> On Mac it worked just fine.
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>
>>>>
>>>>
>>>>
>>>> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I received a question from someone running a 200MB image on Windows
>>>>> using Cog 2361.
>>>>>
>>>>> If I open the image on Mac, it works just fine. Unfortunately, I do
>>>>> not have a Windows machine around, and I cannot test but I believe it
>>>>> should be solvable by increasing the allocated memory.
>>>>>
>>>>> On Mac, I would run it with: ./Croquet -memory 1500m
>>>>>
>>>>> Can anyone help me with the right incantation for Windows?
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "What we can governs what we wish."
>>>>>
>>>>>
>>>>>
>>>>> <Space is low.png>
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "Yesterday is a fact.
>>>> Tomorrow is a possibility.
>>>> Today is a challenge."
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> --
>>> Mariano
>>> http://marianopeck.wordpress.com
>>>
>>
>
> --
> www.tudorgirba.com
>
> "Beauty is where we see it."
>
>
>
>
>
>
>
>

--
www.tudorgirba.com

"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."


Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Mariano Martinez Peck


On Thu, Apr 21, 2011 at 10:21 PM, Tudor Girba <[hidden email]> wrote:
Hi,

Should I to understand that the only way to enable more memory is to recompile the VM? Does that mean that there is no way to pass this information as a parameter like we can on Mac?


As far as I know you can pass a parameter, but even so, it won't be able to allocate more than 512MB.
I can compile the VM for you with this change in 5 minutes. But I am not sure that such simple code would make it work. I think such limit is there because of something. Otherwise, it sounds stupid imposing a limit just because.

The problem is that I cannot recompile the VM because I have no access to a Windows machine. Is there one available that provides more memory?


I don't think so, but start cc'ing the VM mailing list. You'd probably receive more help.

Cheers

Mariano
 
Cheers,
Doru


On 21 Apr 2011, at 22:09, Alain_Rastoul wrote:

> Hi Tudor,
>
> There is a constant in sqWin32Alloc.h (platforms\win32\vm) :
> #define MAX_VIRTUAL_MEMORY 512*1024*1024
> you can change it to whatever you want and rebuild the vm,
> for exzmple give all the available memory less 256 M .
>
> HTH
>
> Regards
> Alain
>
> "Tudor Girba" <[hidden email]> a écrit
> dans le message de news: [hidden email]...
> Hi,
>
> We have no specific startUp: methods in Moose. In any case, the issue with
> opening the image does not seem to be related to startUp:.
>
> Is it really true that the Cog VM is limited to 512MB of memory?
>
> Cheers,
> Doru
>
>
> On 21 Apr 2011, at 14:27, Luc Fabresse wrote:
>
>> Hi Doru,
>>
>> 2011/4/21 Tudor Girba
>> <[hidden email]>
>> Hi,
>>
>>
>>
>> On Apr 21, 2011, at 14:06, Mariano Martinez Peck
>> <[hidden email]> wrote:
>>
>>>
>>>
>>> On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba
>>> <[hidden email]> wrote:
>>>> Hi again,
>>>>
>>>> I did not say what the problem was :). The problem was that when
>>>> opening the image on Windows, he got a Space is low message and the
>>>> image was not usable (see attachment).
>>>
>>> That's weird. Does moose have something on the startup list?   something
>>> that can be bothering there?
>>
>> Not that I know of. Is there a way to check this?
>>
>> Classes should be registered using Smalltlak addToStartUpList: aClass
>> Then aClass class>>#startUp: is executed at startup.
>> So implementors of #startUp: on Moose classes should give you the answer.
>>
>> #Luc
>>
>>
>> Actually, using exactly the same process some days ago he produced an
>> image of 190MB. This one works just fine on Windows. The only difference
>> between the two is the size of the loaded data.
>>
>> It would be really bad news if the Windows vm would be so severely limited
>> in terms of memory.
>>
>> Cheers,
>> Doru
>>
>>
>>>
>>> On Mac it worked just fine.
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>
>>>>
>>>>
>>>>
>>>> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I received a question from someone running a 200MB image on Windows
>>>>> using Cog 2361.
>>>>>
>>>>> If I open the image on Mac, it works just fine. Unfortunately, I do
>>>>> not have a Windows machine around, and I cannot test but I believe it
>>>>> should be solvable by increasing the allocated memory.
>>>>>
>>>>> On Mac, I would run it with: ./Croquet -memory 1500m
>>>>>
>>>>> Can anyone help me with the right incantation for Windows?
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "What we can governs what we wish."
>>>>>
>>>>>
>>>>>
>>>>> <Space is low.png>
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "Yesterday is a fact.
>>>> Tomorrow is a possibility.
>>>> Today is a challenge."
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> --
>>> Mariano
>>> http://marianopeck.wordpress.com
>>>
>>
>
> --
> www.tudorgirba.com
>
> "Beauty is where we see it."
>
>
>
>
>
>
>
>

--
www.tudorgirba.com

"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."





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

Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Alain rastoul
In reply to this post by Tudor Girba
Mmm, you are right, in old squeak versions, there was a parameter
-memory: xx (xx inMB)
but I don't know if it is still in use.

BTW there must be some hanging references in memory and perhaps youd should
do some PointerFinder on it.
A very handy script I found (on Ramon Leon's blog or elsewhere I don't
remember) could help you.
You can try it in a workspace and see if it reduces your memory usage (after
save and quit)
comment unknown or unwanted commands :
   | tasks |
    tasks := OrderedCollection new
                add: [MCFileBasedRepository flushAllCaches];
                add: [WARegistry clearAllHandlers];
               " add: [SMSqueakMap default clearCaches];"
                add: [Smalltalk removeEmptyMessageCategories];
                add: [Workspace
                        allSubInstancesDo: [:each | each setBindings:
Dictionary new]];
               " add: [Undeclared removeUnreferencedKeys];"
               " add: [Categorizer sortAllCategories];"
                add: [ODBCConnection cleanAll];
                add: [Symbol compactSymbolTable];
               " add: [ReleaseBuilderDeveloper new fixObsoleteReferences];"
                add: [Smalltalk garbageCollectMost];
                add: [Smalltalk garbageCollect ];
                add: [Smalltalk garbageCollect ];
                add: [Smalltalk garbageCollect ];
  add: [EventManager actionMaps keys do: [:each| EventManager
releaseActionMapFor: each] ];
  add: [Debugger closeAllDebuggers];
  add:[Debugger allInstances do: [ :d | d release ] ];

                 yourself.
    UIManager default
        informUserDuring: [:bar | tasks
                do: [:block |
                    bar value: block printString.
                    [block value]
                        on: Error
                        do: [:error | Transcript show: error;
                                 cr]]].

Regards
Alain

"Tudor Girba" <[hidden email]> a écrit
dans le message de news: [hidden email]...
Hi,

Should I to understand that the only way to enable more memory is to
recompile the VM? Does that mean that there is no way to pass this
information as a parameter like we can on Mac?

The problem is that I cannot recompile the VM because I have no access to a
Windows machine. Is there one available that provides more memory?

Cheers,
Doru


On 21 Apr 2011, at 22:09, Alain_Rastoul wrote:

> Hi Tudor,
>
> There is a constant in sqWin32Alloc.h (platforms\win32\vm) :
> #define MAX_VIRTUAL_MEMORY 512*1024*1024
> you can change it to whatever you want and rebuild the vm,
> for exzmple give all the available memory less 256 M .
>
> HTH
>
> Regards
> Alain
>
> "Tudor Girba" <[hidden email]> a
> écrit
> dans le message de news:
> [hidden email]...
> Hi,
>
> We have no specific startUp: methods in Moose. In any case, the issue with
> opening the image does not seem to be related to startUp:.
>
> Is it really true that the Cog VM is limited to 512MB of memory?
>
> Cheers,
> Doru
>
>
> On 21 Apr 2011, at 14:27, Luc Fabresse wrote:
>
>> Hi Doru,
>>
>> 2011/4/21 Tudor Girba
>> <[hidden email]>
>> Hi,
>>
>>
>>
>> On Apr 21, 2011, at 14:06, Mariano Martinez Peck
>> <[hidden email]> wrote:
>>
>>>
>>>
>>> On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba
>>> <[hidden email]> wrote:
>>>> Hi again,
>>>>
>>>> I did not say what the problem was :). The problem was that when
>>>> opening the image on Windows, he got a Space is low message and the
>>>> image was not usable (see attachment).
>>>
>>> That's weird. Does moose have something on the startup list?   something
>>> that can be bothering there?
>>
>> Not that I know of. Is there a way to check this?
>>
>> Classes should be registered using Smalltlak addToStartUpList: aClass
>> Then aClass class>>#startUp: is executed at startup.
>> So implementors of #startUp: on Moose classes should give you the answer.
>>
>> #Luc
>>
>>
>> Actually, using exactly the same process some days ago he produced an
>> image of 190MB. This one works just fine on Windows. The only difference
>> between the two is the size of the loaded data.
>>
>> It would be really bad news if the Windows vm would be so severely
>> limited
>> in terms of memory.
>>
>> Cheers,
>> Doru
>>
>>
>>>
>>> On Mac it worked just fine.
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>
>>>>
>>>>
>>>>
>>>> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I received a question from someone running a 200MB image on Windows
>>>>> using Cog 2361.
>>>>>
>>>>> If I open the image on Mac, it works just fine. Unfortunately, I do
>>>>> not have a Windows machine around, and I cannot test but I believe it
>>>>> should be solvable by increasing the allocated memory.
>>>>>
>>>>> On Mac, I would run it with: ./Croquet -memory 1500m
>>>>>
>>>>> Can anyone help me with the right incantation for Windows?
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "What we can governs what we wish."
>>>>>
>>>>>
>>>>>
>>>>> <Space is low.png>
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "Yesterday is a fact.
>>>> Tomorrow is a possibility.
>>>> Today is a challenge."
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> --
>>> Mariano
>>> http://marianopeck.wordpress.com
>>>
>>
>
> --
> www.tudorgirba.com
>
> "Beauty is where we see it."
>
>
>
>
>
>
>
>

--
www.tudorgirba.com

"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."






Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Mariano Martinez Peck
Alain: as far as I understood, he cannot even start the image...so he won't be able to open a workspace and evaluate something.

Doru, if you can evaluate something in a workspace, you may also try SpaceTally new printSpaceAnalysis
and then check the STspace.text  that is next to the image. That way you acn see if there are certain classes that have a lot of instances.

Can you evaluate "Smalltalk garbageCollect " and tell me the answer?  just curious....

thanks

mariano

On Thu, Apr 21, 2011 at 10:36 PM, Alain_Rastoul <[hidden email]> wrote:
Mmm, you are right, in old squeak versions, there was a parameter
-memory: xx (xx inMB)
but I don't know if it is still in use.

BTW there must be some hanging references in memory and perhaps youd should
do some PointerFinder on it.
A very handy script I found (on Ramon Leon's blog or elsewhere I don't
remember) could help you.
You can try it in a workspace and see if it reduces your memory usage (after
save and quit)
comment unknown or unwanted commands :
  | tasks |
   tasks := OrderedCollection new
               add: [MCFileBasedRepository flushAllCaches];
               add: [WARegistry clearAllHandlers];
              " add: [SMSqueakMap default clearCaches];"
               add: [Smalltalk removeEmptyMessageCategories];
               add: [Workspace
                       allSubInstancesDo: [:each | each setBindings:
Dictionary new]];
              " add: [Undeclared removeUnreferencedKeys];"
              " add: [Categorizer sortAllCategories];"
               add: [ODBCConnection cleanAll];
               add: [Symbol compactSymbolTable];
              " add: [ReleaseBuilderDeveloper new fixObsoleteReferences];"
               add: [Smalltalk garbageCollectMost];
               add: [Smalltalk garbageCollect ];
               add: [Smalltalk garbageCollect ];
               add: [Smalltalk garbageCollect ];
 add: [EventManager actionMaps keys do: [:each| EventManager
releaseActionMapFor: each] ];
 add: [Debugger closeAllDebuggers];
 add:[Debugger allInstances do: [ :d | d release ] ];

                yourself.
   UIManager default
       informUserDuring: [:bar | tasks
               do: [:block |
                   bar value: block printString.
                   [block value]
                       on: Error
                       do: [:error | Transcript show: error;
                                cr]]].

Regards
Alain

"Tudor Girba" <[hidden email]> a écrit
dans le message de news: [hidden email]...
Hi,

Should I to understand that the only way to enable more memory is to
recompile the VM? Does that mean that there is no way to pass this
information as a parameter like we can on Mac?

The problem is that I cannot recompile the VM because I have no access to a
Windows machine. Is there one available that provides more memory?

Cheers,
Doru


On 21 Apr 2011, at 22:09, Alain_Rastoul wrote:

> Hi Tudor,
>
> There is a constant in sqWin32Alloc.h (platforms\win32\vm) :
> #define MAX_VIRTUAL_MEMORY 512*1024*1024
> you can change it to whatever you want and rebuild the vm,
> for exzmple give all the available memory less 256 M .
>
> HTH
>
> Regards
> Alain
>
> "Tudor Girba" <[hidden email]> a
> écrit
> dans le message de news:
> [hidden email]...
> Hi,
>
> We have no specific startUp: methods in Moose. In any case, the issue with
> opening the image does not seem to be related to startUp:.
>
> Is it really true that the Cog VM is limited to 512MB of memory?
>
> Cheers,
> Doru
>
>
> On 21 Apr 2011, at 14:27, Luc Fabresse wrote:
>
>> Hi Doru,
>>
>> 2011/4/21 Tudor Girba
>> <[hidden email]>
>> Hi,
>>
>>
>>
>> On Apr 21, 2011, at 14:06, Mariano Martinez Peck
>> <[hidden email]> wrote:
>>
>>>
>>>
>>> On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba
>>> <[hidden email]> wrote:
>>>> Hi again,
>>>>
>>>> I did not say what the problem was :). The problem was that when
>>>> opening the image on Windows, he got a Space is low message and the
>>>> image was not usable (see attachment).
>>>
>>> That's weird. Does moose have something on the startup list?   something
>>> that can be bothering there?
>>
>> Not that I know of. Is there a way to check this?
>>
>> Classes should be registered using Smalltlak addToStartUpList: aClass
>> Then aClass class>>#startUp: is executed at startup.
>> So implementors of #startUp: on Moose classes should give you the answer.
>>
>> #Luc
>>
>>
>> Actually, using exactly the same process some days ago he produced an
>> image of 190MB. This one works just fine on Windows. The only difference
>> between the two is the size of the loaded data.
>>
>> It would be really bad news if the Windows vm would be so severely
>> limited
>> in terms of memory.
>>
>> Cheers,
>> Doru
>>
>>
>>>
>>> On Mac it worked just fine.
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>
>>>>
>>>>
>>>>
>>>> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I received a question from someone running a 200MB image on Windows
>>>>> using Cog 2361.
>>>>>
>>>>> If I open the image on Mac, it works just fine. Unfortunately, I do
>>>>> not have a Windows machine around, and I cannot test but I believe it
>>>>> should be solvable by increasing the allocated memory.
>>>>>
>>>>> On Mac, I would run it with: ./Croquet -memory 1500m
>>>>>
>>>>> Can anyone help me with the right incantation for Windows?
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "What we can governs what we wish."
>>>>>
>>>>>
>>>>>
>>>>> <Space is low.png>
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "Yesterday is a fact.
>>>> Tomorrow is a possibility.
>>>> Today is a challenge."
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> --
>>> Mariano
>>> http://marianopeck.wordpress.com
>>>
>>
>
> --
> www.tudorgirba.com
>
> "Beauty is where we see it."
>
>
>
>
>
>
>
>

--
www.tudorgirba.com

"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."









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

Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Alain rastoul
In reply to this post by Mariano Martinez Peck
Apparently, the vm allocates MAX_VIRTUAL_MEMORY and reduces by steps of 128M until it
succeeds.
so I suppose it could be possible to allocate 2Gb and see how it runs on a 1Gb system and if this is not too much stress for
the system (thinking of the pagefile) ?
Tudor is your vm a cog or non cog vm ?
 
"Mariano Martinez Peck" <[hidden email]> a écrit dans le message de news: [hidden email]...




On Thu, Apr 21, 2011 at 10:21 PM, Tudor Girba <[hidden email]> wrote:
Hi,

Should I to understand that the only way to enable more memory is to recompile the VM? Does that mean that there is no way to pass this information as a parameter like we can on Mac?


As far as I know you can pass a parameter, but even so, it won't be able to allocate more than 512MB.
I can compile the VM for you with this change in 5 minutes. But I am not sure that such simple code would make it work. I think such limit is there because of something. Otherwise, it sounds stupid imposing a limit just because.

The problem is that I cannot recompile the VM because I have no access to a Windows machine. Is there one available that provides more memory?


I don't think so, but start cc'ing the VM mailing list. You'd probably receive more help.

Cheers

Mariano
 
Cheers,
Doru


On 21 Apr 2011, at 22:09, Alain_Rastoul wrote:

> Hi Tudor,
>
> There is a constant in sqWin32Alloc.h (platforms\win32\vm) :
> #define MAX_VIRTUAL_MEMORY 512*1024*1024
> you can change it to whatever you want and rebuild the vm,
> for exzmple give all the available memory less 256 M .
>
> HTH
>
> Regards
> Alain
>
> "Tudor Girba" <[hidden email]> a écrit
> dans le message de news: [hidden email]...
> Hi,
>
> We have no specific startUp: methods in Moose. In any case, the issue with
> opening the image does not seem to be related to startUp:.
>
> Is it really true that the Cog VM is limited to 512MB of memory?
>
> Cheers,
> Doru
>
>
> On 21 Apr 2011, at 14:27, Luc Fabresse wrote:
>
>> Hi Doru,
>>
>> 2011/4/21 Tudor Girba
>> <[hidden email]>
>> Hi,
>>
>>
>>
>> On Apr 21, 2011, at 14:06, Mariano Martinez Peck
>> <[hidden email]> wrote:
>>
>>>
>>>
>>> On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba
>>> <[hidden email]> wrote:
>>>> Hi again,
>>>>
>>>> I did not say what the problem was :). The problem was that when
>>>> opening the image on Windows, he got a Space is low message and the
>>>> image was not usable (see attachment).
>>>
>>> That's weird. Does moose have something on the startup list?   something
>>> that can be bothering there?
>>
>> Not that I know of. Is there a way to check this?
>>
>> Classes should be registered using Smalltlak addToStartUpList: aClass
>> Then aClass class>>#startUp: is executed at startup.
>> So implementors of #startUp: on Moose classes should give you the answer.
>>
>> #Luc
>>
>>
>> Actually, using exactly the same process some days ago he produced an
>> image of 190MB. This one works just fine on Windows. The only difference
>> between the two is the size of the loaded data.
>>
>> It would be really bad news if the Windows vm would be so severely limited
>> in terms of memory.
>>
>> Cheers,
>> Doru
>>
>>
>>>
>>> On Mac it worked just fine.
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>
>>>>
>>>>
>>>>
>>>> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I received a question from someone running a 200MB image on Windows
>>>>> using Cog 2361.
>>>>>
>>>>> If I open the image on Mac, it works just fine. Unfortunately, I do
>>>>> not have a Windows machine around, and I cannot test but I believe it
>>>>> should be solvable by increasing the allocated memory.
>>>>>
>>>>> On Mac, I would run it with: ./Croquet -memory 1500m
>>>>>
>>>>> Can anyone help me with the right incantation for Windows?
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "What we can governs what we wish."
>>>>>
>>>>>
>>>>>
>>>>> <Space is low.png>
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "Yesterday is a fact.
>>>> Tomorrow is a possibility.
>>>> Today is a challenge."
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> --
>>> Mariano
>>> http://marianopeck.wordpress.com
>>>
>>
>
> --
> www.tudorgirba.com
>
> "Beauty is where we see it."
>
>
>
>
>
>
>
>

--
www.tudorgirba.com

"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."





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

Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Mariano Martinez Peck


On Thu, Apr 21, 2011 at 10:44 PM, Alain_Rastoul <[hidden email]> wrote:
Apparently, the vm allocates MAX_VIRTUAL_MEMORY and reduces by steps of 128M until it
succeeds.
so I suppose it could be possible to allocate 2Gb and see how it runs on a 1Gb system and if this is not too much stress for
the system (thinking of the pagefile) ?
Tudor is your vm a cog or non cog vm ?

Cog
 
 
"Mariano Martinez Peck" <[hidden email]> a écrit dans le message de news: [hidden email]...




On Thu, Apr 21, 2011 at 10:21 PM, Tudor Girba <[hidden email]> wrote:
Hi,

Should I to understand that the only way to enable more memory is to recompile the VM? Does that mean that there is no way to pass this information as a parameter like we can on Mac?


As far as I know you can pass a parameter, but even so, it won't be able to allocate more than 512MB.
I can compile the VM for you with this change in 5 minutes. But I am not sure that such simple code would make it work. I think such limit is there because of something. Otherwise, it sounds stupid imposing a limit just because.

The problem is that I cannot recompile the VM because I have no access to a Windows machine. Is there one available that provides more memory?


I don't think so, but start cc'ing the VM mailing list. You'd probably receive more help.

Cheers

Mariano
 
Cheers,
Doru


On 21 Apr 2011, at 22:09, Alain_Rastoul wrote:

> Hi Tudor,
>
> There is a constant in sqWin32Alloc.h (platforms\win32\vm) :
> #define MAX_VIRTUAL_MEMORY 512*1024*1024
> you can change it to whatever you want and rebuild the vm,
> for exzmple give all the available memory less 256 M .
>
> HTH
>
> Regards
> Alain
>
> "Tudor Girba" <[hidden email]> a écrit
> dans le message de news: [hidden email]...
> Hi,
>
> We have no specific startUp: methods in Moose. In any case, the issue with
> opening the image does not seem to be related to startUp:.
>
> Is it really true that the Cog VM is limited to 512MB of memory?
>
> Cheers,
> Doru
>
>
> On 21 Apr 2011, at 14:27, Luc Fabresse wrote:
>
>> Hi Doru,
>>
>> 2011/4/21 Tudor Girba
>> <[hidden email]>
>> Hi,
>>
>>
>>
>> On Apr 21, 2011, at 14:06, Mariano Martinez Peck
>> <[hidden email]> wrote:
>>
>>>
>>>
>>> On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba
>>> <[hidden email]> wrote:
>>>> Hi again,
>>>>
>>>> I did not say what the problem was :). The problem was that when
>>>> opening the image on Windows, he got a Space is low message and the
>>>> image was not usable (see attachment).
>>>
>>> That's weird. Does moose have something on the startup list?   something
>>> that can be bothering there?
>>
>> Not that I know of. Is there a way to check this?
>>
>> Classes should be registered using Smalltlak addToStartUpList: aClass
>> Then aClass class>>#startUp: is executed at startup.
>> So implementors of #startUp: on Moose classes should give you the answer.
>>
>> #Luc
>>
>>
>> Actually, using exactly the same process some days ago he produced an
>> image of 190MB. This one works just fine on Windows. The only difference
>> between the two is the size of the loaded data.
>>
>> It would be really bad news if the Windows vm would be so severely limited
>> in terms of memory.
>>
>> Cheers,
>> Doru
>>
>>
>>>
>>> On Mac it worked just fine.
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>
>>>>
>>>>
>>>>
>>>> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I received a question from someone running a 200MB image on Windows
>>>>> using Cog 2361.
>>>>>
>>>>> If I open the image on Mac, it works just fine. Unfortunately, I do
>>>>> not have a Windows machine around, and I cannot test but I believe it
>>>>> should be solvable by increasing the allocated memory.
>>>>>
>>>>> On Mac, I would run it with: ./Croquet -memory 1500m
>>>>>
>>>>> Can anyone help me with the right incantation for Windows?
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "What we can governs what we wish."
>>>>>
>>>>>
>>>>>
>>>>> <Space is low.png>
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "Yesterday is a fact.
>>>> Tomorrow is a possibility.
>>>> Today is a challenge."
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> --
>>> Mariano
>>> http://marianopeck.wordpress.com
>>>
>>
>
> --
> www.tudorgirba.com
>
> "Beauty is where we see it."
>
>
>
>
>
>
>
>

--
www.tudorgirba.com

"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."





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




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

Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Marcus Denker-4
In reply to this post by Alain rastoul

On Apr 21, 2011, at 10:22 PM, Tudor Girba wrote:

> Hi,
>
> Should I to understand that the only way to enable more memory is to recompile the VM? Does that mean that there is no way to pass this information as a parameter like we can on Mac?
>
> The problem is that I cannot recompile the VM because I have no access to a Windows machine. Is there one available that provides more memory?
>

We need to finish the windows auto build setup...


--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.


Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Alain rastoul
In reply to this post by Mariano Martinez Peck
I thought he was able to start it on a Mac that's why I suggested to this on a Mac and see if memory consumption was reduced.
BTW I have rebuild a cog vm with 2Gb ram for MAX_MEMORY and it runs ok on my 1Gb netbook
 
"Mariano Martinez Peck" <[hidden email]> a écrit dans le message de news: [hidden email]...
Alain: as far as I understood, he cannot even start the image...so he won't be able to open a workspace and evaluate something.

Doru, if you can evaluate something in a workspace, you may also try SpaceTally new printSpaceAnalysis
and then check the STspace.text  that is next to the image. That way you acn see if there are certain classes that have a lot of instances.

Can you evaluate "Smalltalk garbageCollect " and tell me the answer?  just curious....

thanks

mariano

On Thu, Apr 21, 2011 at 10:36 PM, Alain_Rastoul <[hidden email]> wrote:
Mmm, you are right, in old squeak versions, there was a parameter
-memory: xx (xx inMB)
but I don't know if it is still in use.

BTW there must be some hanging references in memory and perhaps youd should
do some PointerFinder on it.
A very handy script I found (on Ramon Leon's blog or elsewhere I don't
remember) could help you.
You can try it in a workspace and see if it reduces your memory usage (after
save and quit)
comment unknown or unwanted commands :
  | tasks |
   tasks := OrderedCollection new
               add: [MCFileBasedRepository flushAllCaches];
               add: [WARegistry clearAllHandlers];
              " add: [SMSqueakMap default clearCaches];"
               add: [Smalltalk removeEmptyMessageCategories];
               add: [Workspace
                       allSubInstancesDo: [:each | each setBindings:
Dictionary new]];
              " add: [Undeclared removeUnreferencedKeys];"
              " add: [Categorizer sortAllCategories];"
               add: [ODBCConnection cleanAll];
               add: [Symbol compactSymbolTable];
              " add: [ReleaseBuilderDeveloper new fixObsoleteReferences];"
               add: [Smalltalk garbageCollectMost];
               add: [Smalltalk garbageCollect ];
               add: [Smalltalk garbageCollect ];
               add: [Smalltalk garbageCollect ];
 add: [EventManager actionMaps keys do: [:each| EventManager
releaseActionMapFor: each] ];
 add: [Debugger closeAllDebuggers];
 add:[Debugger allInstances do: [ :d | d release ] ];

                yourself.
   UIManager default
       informUserDuring: [:bar | tasks
               do: [:block |
                   bar value: block printString.
                   [block value]
                       on: Error
                       do: [:error | Transcript show: error;
                                cr]]].

Regards
Alain

"Tudor Girba" <[hidden email]> a écrit
dans le message de news: [hidden email]...
Hi,

Should I to understand that the only way to enable more memory is to
recompile the VM? Does that mean that there is no way to pass this
information as a parameter like we can on Mac?

The problem is that I cannot recompile the VM because I have no access to a
Windows machine. Is there one available that provides more memory?

Cheers,
Doru


On 21 Apr 2011, at 22:09, Alain_Rastoul wrote:

> Hi Tudor,
>
> There is a constant in sqWin32Alloc.h (platforms\win32\vm) :
> #define MAX_VIRTUAL_MEMORY 512*1024*1024
> you can change it to whatever you want and rebuild the vm,
> for exzmple give all the available memory less 256 M .
>
> HTH
>
> Regards
> Alain
>
> "Tudor Girba" <[hidden email]> a
> écrit
> dans le message de news:
> [hidden email]
> Hi,
>
> We have no specific startUp: methods in Moose. In any case, the issue with
> opening the image does not seem to be related to startUp:.
>
> Is it really true that the Cog VM is limited to 512MB of memory?
>
> Cheers,
> Doru
>
>
> On 21 Apr 2011, at 14:27, Luc Fabresse wrote:
>
>> Hi Doru,
>>
>> 2011/4/21 Tudor Girba
>> <[hidden email]>
>> Hi,
>>
>>
>>
>> On Apr 21, 2011, at 14:06, Mariano Martinez Peck
>> <[hidden email]> wrote:
>>
>>>
>>>
>>> On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba
>>> <[hidden email]> wrote:
>>>> Hi again,
>>>>
>>>> I did not say what the problem was :). The problem was that when
>>>> opening the image on Windows, he got a Space is low message and the
>>>> image was not usable (see attachment).
>>>
>>> That's weird. Does moose have something on the startup list?   something
>>> that can be bothering there?
>>
>> Not that I know of. Is there a way to check this?
>>
>> Classes should be registered using Smalltlak addToStartUpList: aClass
>> Then aClass class>>#startUp: is executed at startup.
>> So implementors of #startUp: on Moose classes should give you the answer.
>>
>> #Luc
>>
>>
>> Actually, using exactly the same process some days ago he produced an
>> image of 190MB. This one works just fine on Windows. The only difference
>> between the two is the size of the loaded data.
>>
>> It would be really bad news if the Windows vm would be so severely
>> limited
>> in terms of memory.
>>
>> Cheers,
>> Doru
>>
>>
>>>
>>> On Mac it worked just fine.
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>
>>>>
>>>>
>>>>
>>>> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I received a question from someone running a 200MB image on Windows
>>>>> using Cog 2361.
>>>>>
>>>>> If I open the image on Mac, it works just fine. Unfortunately, I do
>>>>> not have a Windows machine around, and I cannot test but I believe it
>>>>> should be solvable by increasing the allocated memory.
>>>>>
>>>>> On Mac, I would run it with: ./Croquet -memory 1500m
>>>>>
>>>>> Can anyone help me with the right incantation for Windows?
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "What we can governs what we wish."
>>>>>
>>>>>
>>>>>
>>>>> <Space is low.png>
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "Yesterday is a fact.
>>>> Tomorrow is a possibility.
>>>> Today is a challenge."
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> --
>>> Mariano
>>> http://marianopeck.wordpress.com
>>>
>>
>
> --
> www.tudorgirba.com
>
> "Beauty is where we see it."
>
>
>
>
>
>
>
>

--
www.tudorgirba.com

"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."









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

Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Alain rastoul
(And of course Tudor, I forgot to mention it but I can send you this vm if you need)
 
"Alain_Rastoul" <[hidden email]> a écrit dans le message de news: [hidden email]...
I thought he was able to start it on a Mac that's why I suggested to this on a Mac and see if memory consumption was reduced.
BTW I have rebuild a cog vm with 2Gb ram for MAX_MEMORY and it runs ok on my 1Gb netbook
 
"Mariano Martinez Peck" <[hidden email]> a écrit dans le message de news: [hidden email]...
Alain: as far as I understood, he cannot even start the image...so he won't be able to open a workspace and evaluate something.

Doru, if you can evaluate something in a workspace, you may also try SpaceTally new printSpaceAnalysis
and then check the STspace.text  that is next to the image. That way you acn see if there are certain classes that have a lot of instances.

Can you evaluate "Smalltalk garbageCollect " and tell me the answer?  just curious....

thanks

mariano

On Thu, Apr 21, 2011 at 10:36 PM, Alain_Rastoul <[hidden email]> wrote:
Mmm, you are right, in old squeak versions, there was a parameter
-memory: xx (xx inMB)
but I don't know if it is still in use.

BTW there must be some hanging references in memory and perhaps youd should
do some PointerFinder on it.
A very handy script I found (on Ramon Leon's blog or elsewhere I don't
remember) could help you.
You can try it in a workspace and see if it reduces your memory usage (after
save and quit)
comment unknown or unwanted commands :
  | tasks |
   tasks := OrderedCollection new
               add: [MCFileBasedRepository flushAllCaches];
               add: [WARegistry clearAllHandlers];
              " add: [SMSqueakMap default clearCaches];"
               add: [Smalltalk removeEmptyMessageCategories];
               add: [Workspace
                       allSubInstancesDo: [:each | each setBindings:
Dictionary new]];
              " add: [Undeclared removeUnreferencedKeys];"
              " add: [Categorizer sortAllCategories];"
               add: [ODBCConnection cleanAll];
               add: [Symbol compactSymbolTable];
              " add: [ReleaseBuilderDeveloper new fixObsoleteReferences];"
               add: [Smalltalk garbageCollectMost];
               add: [Smalltalk garbageCollect ];
               add: [Smalltalk garbageCollect ];
               add: [Smalltalk garbageCollect ];
 add: [EventManager actionMaps keys do: [:each| EventManager
releaseActionMapFor: each] ];
 add: [Debugger closeAllDebuggers];
 add:[Debugger allInstances do: [ :d | d release ] ];

                yourself.
   UIManager default
       informUserDuring: [:bar | tasks
               do: [:block |
                   bar value: block printString.
                   [block value]
                       on: Error
                       do: [:error | Transcript show: error;
                                cr]]].

Regards
Alain

"Tudor Girba" <[hidden email]> a écrit
dans le message de news: [hidden email]
Hi,

Should I to understand that the only way to enable more memory is to
recompile the VM? Does that mean that there is no way to pass this
information as a parameter like we can on Mac?

The problem is that I cannot recompile the VM because I have no access to a
Windows machine. Is there one available that provides more memory?

Cheers,
Doru


On 21 Apr 2011, at 22:09, Alain_Rastoul wrote:

> Hi Tudor,
>
> There is a constant in sqWin32Alloc.h (platforms\win32\vm) :
> #define MAX_VIRTUAL_MEMORY 512*1024*1024
> you can change it to whatever you want and rebuild the vm,
> for exzmple give all the available memory less 256 M .
>
> HTH
>
> Regards
> Alain
>
> "Tudor Girba" <[hidden email]> a
> écrit
> dans le message de news:
> [hidden email]
> Hi,
>
> We have no specific startUp: methods in Moose. In any case, the issue with
> opening the image does not seem to be related to startUp:.
>
> Is it really true that the Cog VM is limited to 512MB of memory?
>
> Cheers,
> Doru
>
>
> On 21 Apr 2011, at 14:27, Luc Fabresse wrote:
>
>> Hi Doru,
>>
>> 2011/4/21 Tudor Girba
>> <[hidden email]>
>> Hi,
>>
>>
>>
>> On Apr 21, 2011, at 14:06, Mariano Martinez Peck
>> <[hidden email]> wrote:
>>
>>>
>>>
>>> On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba
>>> <[hidden email]> wrote:
>>>> Hi again,
>>>>
>>>> I did not say what the problem was :). The problem was that when
>>>> opening the image on Windows, he got a Space is low message and the
>>>> image was not usable (see attachment).
>>>
>>> That's weird. Does moose have something on the startup list?   something
>>> that can be bothering there?
>>
>> Not that I know of. Is there a way to check this?
>>
>> Classes should be registered using Smalltlak addToStartUpList: aClass
>> Then aClass class>>#startUp: is executed at startup.
>> So implementors of #startUp: on Moose classes should give you the answer.
>>
>> #Luc
>>
>>
>> Actually, using exactly the same process some days ago he produced an
>> image of 190MB. This one works just fine on Windows. The only difference
>> between the two is the size of the loaded data.
>>
>> It would be really bad news if the Windows vm would be so severely
>> limited
>> in terms of memory.
>>
>> Cheers,
>> Doru
>>
>>
>>>
>>> On Mac it worked just fine.
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>
>>>>
>>>>
>>>>
>>>> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I received a question from someone running a 200MB image on Windows
>>>>> using Cog 2361.
>>>>>
>>>>> If I open the image on Mac, it works just fine. Unfortunately, I do
>>>>> not have a Windows machine around, and I cannot test but I believe it
>>>>> should be solvable by increasing the allocated memory.
>>>>>
>>>>> On Mac, I would run it with: ./Croquet -memory 1500m
>>>>>
>>>>> Can anyone help me with the right incantation for Windows?
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "What we can governs what we wish."
>>>>>
>>>>>
>>>>>
>>>>> <Space is low.png>
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "Yesterday is a fact.
>>>> Tomorrow is a possibility.
>>>> Today is a challenge."
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>> --
>>> Mariano
>>> http://marianopeck.wordpress.com
>>>
>>
>
> --
> www.tudorgirba.com
>
> "Beauty is where we see it."
>
>
>
>
>
>
>
>

--
www.tudorgirba.com

"If you interrupt the barber while he is cutting your hair,
you will end up with a messy haircut."









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

Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Andres Valloud-4
In reply to this post by Alain rastoul
Yeah, not all operating systems and application environments are the
same.  What happens when you let a 512mb image loose in an environment
where you have 10 images running on a 4gb machine?  Ouch.  What happens
when you let a 2gb image loose in a 1gb machine and you get an infinite
recursion bug?  Ouch.

But, at the same time, a 512mb limit can be useful precisely to prevent
an infinite recursion from killing your machine.  I hate to brag, but I
have been working on memory policies and memory management for quite a
while on VisualWorks, and the edge cases do matter a lot.  It's not so
simple as to "let's just increase the max memory to 4gb".

Also, you can recompile your VMs with different settings and what not,
but how do you know they will work?  Is the compilation environment
standardized somewhere so that I can reproduce an "official" VM build if
I want?

On 4/21/11 13:44 , Alain_Rastoul wrote:

> Apparently, the vm allocates MAX_VIRTUAL_MEMORY and reduces by steps of
> 128M until it
> succeeds.
> so I suppose it could be possible to allocate 2Gb and see how it runs on
> a 1Gb system and if this is not too much stress for
> the system (thinking of the pagefile) ?
> Tudor is your vm a cog or non cog vm ?
>
>     "Mariano Martinez Peck" <[hidden email]
>     <mailto:[hidden email]>> a écrit dans le message de news:
>     BANLkTi=[hidden email]
>     <mailto:BANLkTi=[hidden email]>...
>
>     ------------------------------------------------------------------------
>
>
>
>     On Thu, Apr 21, 2011 at 10:21 PM, Tudor Girba <[hidden email]
>     <mailto:[hidden email]>> wrote:
>
>         Hi,
>
>         Should I to understand that the only way to enable more memory
>         is to recompile the VM? Does that mean that there is no way to
>         pass this information as a parameter like we can on Mac?
>
>
>     As far as I know you can pass a parameter, but even so, it won't be
>     able to allocate more than 512MB.
>     I can compile the VM for you with this change in 5 minutes. But I am
>     not sure that such simple code would make it work. I think such
>     limit is there because of something. Otherwise, it sounds stupid
>     imposing a limit just because.
>
>         The problem is that I cannot recompile the VM because I have no
>         access to a Windows machine. Is there one available that
>         provides more memory?
>
>
>     I don't think so, but start cc'ing the VM mailing list. You'd
>     probably receive more help.
>
>     Cheers
>
>     Mariano
>
>         Cheers,
>         Doru
>
>
>         On 21 Apr 2011, at 22:09, Alain_Rastoul wrote:
>
>          > Hi Tudor,
>          >
>          > There is a constant in sqWin32Alloc.h (platforms\win32\vm) :
>          > #define MAX_VIRTUAL_MEMORY 512*1024*1024
>          > you can change it to whatever you want and rebuild the vm,
>          > for exzmple give all the available memory less 256 M .
>          >
>          > HTH
>          >
>          > Regards
>          > Alain
>          >
>          > "Tudor Girba" <[hidden email]
>         <mailto:[hidden email]>> a écrit
>          > dans le message de news:
>         [hidden email]...
>          > Hi,
>          >
>          > We have no specific startUp: methods in Moose. In any case,
>         the issue with
>          > opening the image does not seem to be related to startUp:.
>          >
>          > Is it really true that the Cog VM is limited to 512MB of memory?
>          >
>          > Cheers,
>          > Doru
>          >
>          >
>          > On 21 Apr 2011, at 14:27, Luc Fabresse wrote:
>          >
>          >> Hi Doru,
>          >>
>          >> 2011/4/21 Tudor Girba
>          >> <[hidden email] <mailto:[hidden email]>>
>          >> Hi,
>          >>
>          >>
>          >>
>          >> On Apr 21, 2011, at 14:06, Mariano Martinez Peck
>          >> <[hidden email] <mailto:[hidden email]>> wrote:
>          >>
>          >>>
>          >>>
>          >>> On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba
>          >>> <[hidden email] <mailto:[hidden email]>> wrote:
>          >>>> Hi again,
>          >>>>
>          >>>> I did not say what the problem was :). The problem was
>         that when
>          >>>> opening the image on Windows, he got a Space is low
>         message and the
>          >>>> image was not usable (see attachment).
>          >>>
>          >>> That's weird. Does moose have something on the startup
>         list? something
>          >>> that can be bothering there?
>          >>
>          >> Not that I know of. Is there a way to check this?
>          >>
>          >> Classes should be registered using Smalltlak
>         addToStartUpList: aClass
>          >> Then aClass class>>#startUp: is executed at startup.
>          >> So implementors of #startUp: on Moose classes should give
>         you the answer.
>          >>
>          >> #Luc
>          >>
>          >>
>          >> Actually, using exactly the same process some days ago he
>         produced an
>          >> image of 190MB. This one works just fine on Windows. The
>         only difference
>          >> between the two is the size of the loaded data.
>          >>
>          >> It would be really bad news if the Windows vm would be so
>         severely limited
>          >> in terms of memory.
>          >>
>          >> Cheers,
>          >> Doru
>          >>
>          >>
>          >>>
>          >>> On Mac it worked just fine.
>          >>>>
>          >>>> Cheers,
>          >>>> Doru
>          >>>>
>          >>>>
>          >>>
>          >>>>
>          >>>>
>          >>>>
>          >>>> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>          >>>>
>          >>>>> Hi,
>          >>>>>
>          >>>>> I received a question from someone running a 200MB image
>         on Windows
>          >>>>> using Cog 2361.
>          >>>>>
>          >>>>> If I open the image on Mac, it works just fine.
>         Unfortunately, I do
>          >>>>> not have a Windows machine around, and I cannot test but
>         I believe it
>          >>>>> should be solvable by increasing the allocated memory.
>          >>>>>
>          >>>>> On Mac, I would run it with: ./Croquet -memory 1500m
>          >>>>>
>          >>>>> Can anyone help me with the right incantation for Windows?
>          >>>>>
>          >>>>> Cheers,
>          >>>>> Doru
>          >>>>>
>          >>>>>
>          >>>>> --
>          >>>>> www.tudorgirba.com <http://www.tudorgirba.com>
>          >>>>>
>          >>>>> "What we can governs what we wish."
>          >>>>>
>          >>>>>
>          >>>>>
>          >>>>> <Space is low.png>
>          >>>>
>          >>>> --
>          >>>> www.tudorgirba.com <http://www.tudorgirba.com>
>          >>>>
>          >>>> "Yesterday is a fact.
>          >>>> Tomorrow is a possibility.
>          >>>> Today is a challenge."
>          >>>>
>          >>>>
>          >>>>
>          >>>
>          >>>
>          >>>
>          >>>
>          >>> --
>          >>> Mariano
>          >>> http://marianopeck.wordpress.com
>          >>>
>          >>
>          >
>          > --
>          > www.tudorgirba.com <http://www.tudorgirba.com>
>          >
>          > "Beauty is where we see it."
>          >
>          >
>          >
>          >
>          >
>          >
>          >
>          >
>
>         --
>         www.tudorgirba.com <http://www.tudorgirba.com>
>
>         "If you interrupt the barber while he is cutting your hair,
>         you will end up with a messy haircut."
>
>
>
>
>
>     --
>     Mariano
>     http://marianopeck.wordpress.com
>

Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Tudor Girba
In reply to this post by Alain rastoul
Hi Alain,

Thanks. I would indeed be interested in your compiled VM.

Regarding running it on Mac, indeed I can do that, but I will have to wait until next week to get access to the image due to holidays.

Another bit of information is that the image was built and saved without a problem on the same machine where now it does not work anymore.

Cheers,
Doru


On 21 Apr 2011, at 23:52, Alain_Rastoul wrote:

> (And of course Tudor, I forgot to mention it but I can send you this vm if you need)
>  
> "Alain_Rastoul" <[hidden email]> a écrit dans le message de news: ioq86o$69j$[hidden email]...
> I thought he was able to start it on a Mac that's why I suggested to this on a Mac and see if memory consumption was reduced.
> BTW I have rebuild a cog vm with 2Gb ram for MAX_MEMORY and it runs ok on my 1Gb netbook
>  
> "Mariano Martinez Peck" <[hidden email]> a écrit dans le message de news:BANLkTikuk1jRV34=[hidden email]...
> Alain: as far as I understood, he cannot even start the image...so he won't be able to open a workspace and evaluate something.
>
> Doru, if you can evaluate something in a workspace, you may also try SpaceTally new printSpaceAnalysis
> and then check the STspace.text  that is next to the image. That way you acn see if there are certain classes that have a lot of instances.
>
> Can you evaluate "Smalltalk garbageCollect " and tell me the answer?  just curious....
>
> thanks
>
> mariano
>
> On Thu, Apr 21, 2011 at 10:36 PM, Alain_Rastoul <[hidden email]> wrote:
> Mmm, you are right, in old squeak versions, there was a parameter
> -memory: xx (xx inMB)
> but I don't know if it is still in use.
>
> BTW there must be some hanging references in memory and perhaps youd should
> do some PointerFinder on it.
> A very handy script I found (on Ramon Leon's blog or elsewhere I don't
> remember) could help you.
> You can try it in a workspace and see if it reduces your memory usage (after
> save and quit)
> comment unknown or unwanted commands :
>   | tasks |
>    tasks := OrderedCollection new
>                add: [MCFileBasedRepository flushAllCaches];
>                add: [WARegistry clearAllHandlers];
>               " add: [SMSqueakMap default clearCaches];"
>                add: [Smalltalk removeEmptyMessageCategories];
>                add: [Workspace
>                        allSubInstancesDo: [:each | each setBindings:
> Dictionary new]];
>               " add: [Undeclared removeUnreferencedKeys];"
>               " add: [Categorizer sortAllCategories];"
>                add: [ODBCConnection cleanAll];
>                add: [Symbol compactSymbolTable];
>               " add: [ReleaseBuilderDeveloper new fixObsoleteReferences];"
>                add: [Smalltalk garbageCollectMost];
>                add: [Smalltalk garbageCollect ];
>                add: [Smalltalk garbageCollect ];
>                add: [Smalltalk garbageCollect ];
>  add: [EventManager actionMaps keys do: [:each| EventManager
> releaseActionMapFor: each] ];
>  add: [Debugger closeAllDebuggers];
>  add:[Debugger allInstances do: [ :d | d release ] ];
>
>                 yourself.
>    UIManager default
>        informUserDuring: [:bar | tasks
>                do: [:block |
>                    bar value: block printString.
>                    [block value]
>                        on: Error
>                        do: [:error | Transcript show: error;
>                                 cr]]].
>
> Regards
> Alain
>
> "Tudor Girba" <[hidden email]> a écrit
> dans le message de news: [hidden email]
> Hi,
>
> Should I to understand that the only way to enable more memory is to
> recompile the VM? Does that mean that there is no way to pass this
> information as a parameter like we can on Mac?
>
> The problem is that I cannot recompile the VM because I have no access to a
> Windows machine. Is there one available that provides more memory?
>
> Cheers,
> Doru
>
>
> On 21 Apr 2011, at 22:09, Alain_Rastoul wrote:
>
> > Hi Tudor,
> >
> > There is a constant in sqWin32Alloc.h (platforms\win32\vm) :
> > #define MAX_VIRTUAL_MEMORY 512*1024*1024
> > you can change it to whatever you want and rebuild the vm,
> > for exzmple give all the available memory less 256 M .
> >
> > HTH
> >
> > Regards
> > Alain
> >
> > "Tudor Girba" <[hidden email]> a
> > écrit
> > dans le message de news:
> > [hidden email]
> > Hi,
> >
> > We have no specific startUp: methods in Moose. In any case, the issue with
> > opening the image does not seem to be related to startUp:.
> >
> > Is it really true that the Cog VM is limited to 512MB of memory?
> >
> > Cheers,
> > Doru
> >
> >
> > On 21 Apr 2011, at 14:27, Luc Fabresse wrote:
> >
> >> Hi Doru,
> >>
> >> 2011/4/21 Tudor Girba
> >> <[hidden email]>
> >> Hi,
> >>
> >>
> >>
> >> On Apr 21, 2011, at 14:06, Mariano Martinez Peck
> >> <[hidden email]> wrote:
> >>
> >>>
> >>>
> >>> On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba
> >>> <[hidden email]> wrote:
> >>>> Hi again,
> >>>>
> >>>> I did not say what the problem was :). The problem was that when
> >>>> opening the image on Windows, he got a Space is low message and the
> >>>> image was not usable (see attachment).
> >>>
> >>> That's weird. Does moose have something on the startup list?   something
> >>> that can be bothering there?
> >>
> >> Not that I know of. Is there a way to check this?
> >>
> >> Classes should be registered using Smalltlak addToStartUpList: aClass
> >> Then aClass class>>#startUp: is executed at startup.
> >> So implementors of #startUp: on Moose classes should give you the answer.
> >>
> >> #Luc
> >>
> >>
> >> Actually, using exactly the same process some days ago he produced an
> >> image of 190MB. This one works just fine on Windows. The only difference
> >> between the two is the size of the loaded data.
> >>
> >> It would be really bad news if the Windows vm would be so severely
> >> limited
> >> in terms of memory.
> >>
> >> Cheers,
> >> Doru
> >>
> >>
> >>>
> >>> On Mac it worked just fine.
> >>>>
> >>>> Cheers,
> >>>> Doru
> >>>>
> >>>>
> >>>
> >>>>
> >>>>
> >>>>
> >>>> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> I received a question from someone running a 200MB image on Windows
> >>>>> using Cog 2361.
> >>>>>
> >>>>> If I open the image on Mac, it works just fine. Unfortunately, I do
> >>>>> not have a Windows machine around, and I cannot test but I believe it
> >>>>> should be solvable by increasing the allocated memory.
> >>>>>
> >>>>> On Mac, I would run it with: ./Croquet -memory 1500m
> >>>>>
> >>>>> Can anyone help me with the right incantation for Windows?
> >>>>>
> >>>>> Cheers,
> >>>>> Doru
> >>>>>
> >>>>>
> >>>>> --
> >>>>> www.tudorgirba.com
> >>>>>
> >>>>> "What we can governs what we wish."
> >>>>>
> >>>>>
> >>>>>
> >>>>> <Space is low.png>
> >>>>
> >>>> --
> >>>> www.tudorgirba.com
> >>>>
> >>>> "Yesterday is a fact.
> >>>> Tomorrow is a possibility.
> >>>> Today is a challenge."
> >>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Mariano
> >>> http://marianopeck.wordpress.com
> >>>
> >>
> >
> > --
> > www.tudorgirba.com
> >
> > "Beauty is where we see it."
> >
> >
> >
> >
> >
> >
> >
> >
>
> --
> www.tudorgirba.com
>
> "If you interrupt the barber while he is cutting your hair,
> you will end up with a messy haircut."
>
>
>
>
>
>
>
>
>
> --
> Mariano
> http://marianopeck.wordpress.com
>

--
www.tudorgirba.com

"We can create beautiful models in a vacuum.
But, to get them effective we have to deal with the inconvenience of reality."


Reply | Threaded
Open this post in threaded view
|

Re: out of memory - cog on windows

Igor Stasenko
On 22 April 2011 10:32, Tudor Girba <[hidden email]> wrote:
> Hi Alain,
>
> Thanks. I would indeed be interested in your compiled VM.
>
> Regarding running it on Mac, indeed I can do that, but I will have to wait until next week to get access to the image due to holidays.
>
> Another bit of information is that the image was built and saved without a problem on the same machine where now it does not work anymore.
>

pass the image to me. i can play with it on windoze.

> Cheers,
> Doru
>
>
> On 21 Apr 2011, at 23:52, Alain_Rastoul wrote:
>
>> (And of course Tudor, I forgot to mention it but I can send you this vm if you need)
>>
>> "Alain_Rastoul" <[hidden email]> a écrit dans le message de news: ioq86o$69j$[hidden email]...
>> I thought he was able to start it on a Mac that's why I suggested to this on a Mac and see if memory consumption was reduced.
>> BTW I have rebuild a cog vm with 2Gb ram for MAX_MEMORY and it runs ok on my 1Gb netbook
>>
>> "Mariano Martinez Peck" <[hidden email]> a écrit dans le message de news:BANLkTikuk1jRV34=[hidden email]...
>> Alain: as far as I understood, he cannot even start the image...so he won't be able to open a workspace and evaluate something.
>>
>> Doru, if you can evaluate something in a workspace, you may also try SpaceTally new printSpaceAnalysis
>> and then check the STspace.text  that is next to the image. That way you acn see if there are certain classes that have a lot of instances.
>>
>> Can you evaluate "Smalltalk garbageCollect " and tell me the answer?  just curious....
>>
>> thanks
>>
>> mariano
>>
>> On Thu, Apr 21, 2011 at 10:36 PM, Alain_Rastoul <[hidden email]> wrote:
>> Mmm, you are right, in old squeak versions, there was a parameter
>> -memory: xx (xx inMB)
>> but I don't know if it is still in use.
>>
>> BTW there must be some hanging references in memory and perhaps youd should
>> do some PointerFinder on it.
>> A very handy script I found (on Ramon Leon's blog or elsewhere I don't
>> remember) could help you.
>> You can try it in a workspace and see if it reduces your memory usage (after
>> save and quit)
>> comment unknown or unwanted commands :
>>   | tasks |
>>    tasks := OrderedCollection new
>>                add: [MCFileBasedRepository flushAllCaches];
>>                add: [WARegistry clearAllHandlers];
>>               " add: [SMSqueakMap default clearCaches];"
>>                add: [Smalltalk removeEmptyMessageCategories];
>>                add: [Workspace
>>                        allSubInstancesDo: [:each | each setBindings:
>> Dictionary new]];
>>               " add: [Undeclared removeUnreferencedKeys];"
>>               " add: [Categorizer sortAllCategories];"
>>                add: [ODBCConnection cleanAll];
>>                add: [Symbol compactSymbolTable];
>>               " add: [ReleaseBuilderDeveloper new fixObsoleteReferences];"
>>                add: [Smalltalk garbageCollectMost];
>>                add: [Smalltalk garbageCollect ];
>>                add: [Smalltalk garbageCollect ];
>>                add: [Smalltalk garbageCollect ];
>>  add: [EventManager actionMaps keys do: [:each| EventManager
>> releaseActionMapFor: each] ];
>>  add: [Debugger closeAllDebuggers];
>>  add:[Debugger allInstances do: [ :d | d release ] ];
>>
>>                 yourself.
>>    UIManager default
>>        informUserDuring: [:bar | tasks
>>                do: [:block |
>>                    bar value: block printString.
>>                    [block value]
>>                        on: Error
>>                        do: [:error | Transcript show: error;
>>                                 cr]]].
>>
>> Regards
>> Alain
>>
>> "Tudor Girba" <[hidden email]> a écrit
>> dans le message de news: [hidden email]
>> Hi,
>>
>> Should I to understand that the only way to enable more memory is to
>> recompile the VM? Does that mean that there is no way to pass this
>> information as a parameter like we can on Mac?
>>
>> The problem is that I cannot recompile the VM because I have no access to a
>> Windows machine. Is there one available that provides more memory?
>>
>> Cheers,
>> Doru
>>
>>
>> On 21 Apr 2011, at 22:09, Alain_Rastoul wrote:
>>
>> > Hi Tudor,
>> >
>> > There is a constant in sqWin32Alloc.h (platforms\win32\vm) :
>> > #define MAX_VIRTUAL_MEMORY 512*1024*1024
>> > you can change it to whatever you want and rebuild the vm,
>> > for exzmple give all the available memory less 256 M .
>> >
>> > HTH
>> >
>> > Regards
>> > Alain
>> >
>> > "Tudor Girba" <[hidden email]> a
>> > écrit
>> > dans le message de news:
>> > [hidden email]
>> > Hi,
>> >
>> > We have no specific startUp: methods in Moose. In any case, the issue with
>> > opening the image does not seem to be related to startUp:.
>> >
>> > Is it really true that the Cog VM is limited to 512MB of memory?
>> >
>> > Cheers,
>> > Doru
>> >
>> >
>> > On 21 Apr 2011, at 14:27, Luc Fabresse wrote:
>> >
>> >> Hi Doru,
>> >>
>> >> 2011/4/21 Tudor Girba
>> >> <[hidden email]>
>> >> Hi,
>> >>
>> >>
>> >>
>> >> On Apr 21, 2011, at 14:06, Mariano Martinez Peck
>> >> <[hidden email]> wrote:
>> >>
>> >>>
>> >>>
>> >>> On Thu, Apr 21, 2011 at 1:58 PM, Tudor Girba
>> >>> <[hidden email]> wrote:
>> >>>> Hi again,
>> >>>>
>> >>>> I did not say what the problem was :). The problem was that when
>> >>>> opening the image on Windows, he got a Space is low message and the
>> >>>> image was not usable (see attachment).
>> >>>
>> >>> That's weird. Does moose have something on the startup list?   something
>> >>> that can be bothering there?
>> >>
>> >> Not that I know of. Is there a way to check this?
>> >>
>> >> Classes should be registered using Smalltlak addToStartUpList: aClass
>> >> Then aClass class>>#startUp: is executed at startup.
>> >> So implementors of #startUp: on Moose classes should give you the answer.
>> >>
>> >> #Luc
>> >>
>> >>
>> >> Actually, using exactly the same process some days ago he produced an
>> >> image of 190MB. This one works just fine on Windows. The only difference
>> >> between the two is the size of the loaded data.
>> >>
>> >> It would be really bad news if the Windows vm would be so severely
>> >> limited
>> >> in terms of memory.
>> >>
>> >> Cheers,
>> >> Doru
>> >>
>> >>
>> >>>
>> >>> On Mac it worked just fine.
>> >>>>
>> >>>> Cheers,
>> >>>> Doru
>> >>>>
>> >>>>
>> >>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> On 21 Apr 2011, at 12:52, Tudor Girba wrote:
>> >>>>
>> >>>>> Hi,
>> >>>>>
>> >>>>> I received a question from someone running a 200MB image on Windows
>> >>>>> using Cog 2361.
>> >>>>>
>> >>>>> If I open the image on Mac, it works just fine. Unfortunately, I do
>> >>>>> not have a Windows machine around, and I cannot test but I believe it
>> >>>>> should be solvable by increasing the allocated memory.
>> >>>>>
>> >>>>> On Mac, I would run it with: ./Croquet -memory 1500m
>> >>>>>
>> >>>>> Can anyone help me with the right incantation for Windows?
>> >>>>>
>> >>>>> Cheers,
>> >>>>> Doru
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> www.tudorgirba.com
>> >>>>>
>> >>>>> "What we can governs what we wish."
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> <Space is low.png>
>> >>>>
>> >>>> --
>> >>>> www.tudorgirba.com
>> >>>>
>> >>>> "Yesterday is a fact.
>> >>>> Tomorrow is a possibility.
>> >>>> Today is a challenge."
>> >>>>
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Mariano
>> >>> http://marianopeck.wordpress.com
>> >>>
>> >>
>> >
>> > --
>> > www.tudorgirba.com
>> >
>> > "Beauty is where we see it."
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>>
>> --
>> www.tudorgirba.com
>>
>> "If you interrupt the barber while he is cutting your hair,
>> you will end up with a messy haircut."
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> Mariano
>> http://marianopeck.wordpress.com
>>
>
> --
> www.tudorgirba.com
>
> "We can create beautiful models in a vacuum.
> But, to get them effective we have to deal with the inconvenience of reality."
>
>
>



--
Best regards,
Igor Stasenko AKA sig.

123