Re: [Pharo-dev] brief explanation of the new class organizer

2013-06-29 Thread stephane ducasse
I love objects but we should consider that they had memory constraints and soon we will have them too because we are starting to have them for Moose ;) Stef What strikes me is why such simple concept, which you can express with couple words: methods in class can have categories, ends up

Re: [Pharo-dev] [ANN] SS3 the canary site

2013-06-29 Thread Stéphane Ducasse
Thanks tobias. To me your version of SS3 looks even more Squeak centric and this is ok but my plate is full and I'm sorry but I focus on Pharo because we must deliver and continue. Now don't you think that joining effort on SmalltalkHub (did you see the name is not PharoHub) would make more

Re: [Pharo-dev] brief explanation of the new class organizer

2013-06-29 Thread Esteban Lorenzano
On Jun 29, 2013, at 9:29 AM, stephane ducasse stephane.duca...@gmail.com wrote: I love objects but we should consider that they had memory constraints and soon we will have them too because we are starting to have them for Moose ;) then we need a better vm/object space/whatever... not to

Re: [Pharo-dev] Question about closure compilation

2013-06-29 Thread Sven Van Caekenberghe
Hi Marcus, On 29 Jun 2013, at 11:12, Marcus Denker marcus.den...@inria.fr wrote: OK, that seems OK. The reason I was asking was because I wanted to know if this JavaScript bug would hit us as well: http://point.davidglasser.net/2013/06/27/surprising-javascript-memory-leak.html It

Re: [Pharo-dev] VM ppa question

2013-06-29 Thread GOUBIER Thierry
Hi Sven, I believe Damien said a while ago to switch to an official' pharo ppa instead of his: deb http://ppa.launchpad.net/pharo/stable/ubuntu raring main (I still have both in my /etc/apt/sources.list.d/ :)) Thierry De : Pharo-dev

Re: [Pharo-dev] Question about closure compilation

2013-06-29 Thread Norbert Hartl
Am 29.06.2013 um 11:12 schrieb Marcus Denker marcus.den...@inria.fr: OK, that seems OK. The reason I was asking was because I wanted to know if this JavaScript bug would hit us as well: http://point.davidglasser.net/2013/06/27/surprising-javascript-memory-leak.html It is slightly

Re: [Pharo-dev] Question about closure compilation

2013-06-29 Thread Marcus Denker
On Jun 29, 2013, at 11:47 AM, Norbert Hartl norb...@hartl.name wrote: Thanks. So please let us separate problems. In the example from Sven there are two problems: - increase of memory per function invocation. That problem we don't have Yes, you are right. I am not really knowledgeable

Re: [Pharo-dev] VM ppa question

2013-06-29 Thread Damien Cassou
On Sat, Jun 29, 2013 at 11:39 AM, GOUBIER Thierry thierry.goub...@cea.fr wrote: I believe Damien said a while ago to switch to an official' pharo ppa instead of his: deb http://ppa.launchpad.net/pharo/stable/ubuntu raring main I think you are right. Users need to delete the old PPA

Re: [Pharo-dev] Exploring Heap Size Limits

2013-06-29 Thread p...@highoctane.be
On OSX Lion w/ 8GB RAM, the first call gives me: [PhilMac:~/Documents/Smalltalk/2-MyWorkspaces/workspaceMemTest philippeback$] ./run.sh memtest.st uptime 0h0m0s memory 25,004,440 bytes old 19,213,728 bytes (76.81%) young 5,384 bytes (0.0%) used 19,219,112 bytes (76.9%) free

Re: [Pharo-dev] Exploring Heap Size Limits

2013-06-29 Thread p...@highoctane.be
I did some more experiments and that's the most I can get from the script, no matter how much free memory there is on the machine. Adding ./pharo --memory 2000m ... has no effect. [PhilMac:~/Documents/Smalltalk/2-MyWorkspaces/workspaceMemTest philippeback$] ./pharo Pharo.image memtest.st 501

Re: [Pharo-dev] VM ppa question

2013-06-29 Thread Sven Van Caekenberghe
Thanks, Theirry, Damien, I did $ sudo rm /etc/apt/sources.list.d/cassou-pharo-quantal.list $ sudo add-apt-repository ppa:pharo/stable $ sudo apt-get update $ sudo apt-get install pharo-vm-core And all seems fine $ pharo-vm-nox --version 3.9-7 #1 Mon Jun 17 09:28:43 UTC 2013 gcc 4.7.2

Re: [Pharo-dev] Exploring Heap Size Limits

2013-06-29 Thread Jan Vrany
Hi, for 32bit application you can never allocate whole 4GB as some memory has to be reserved for kernel. The usual split is 2/2, sometimes 3/1. Plus, the actual code must be somewhere in the memory as well as the stack. Usually the real limit for 32bit application is somewhere like 1.8GB for

[Pharo-dev] Manage a Printer device with Semaphore forMutualExclusion

2013-06-29 Thread Dario Trussardi
Ciao, I work with a seaside application. I have a printer device and i need to manage the use of it at one work at time. I think to use one Semaphore forMutualExclusion defined as variable of the specific printerTicket device Now i defined this code to

Re: [Pharo-dev] Exploring Heap Size Limits

2013-06-29 Thread Sven Van Caekenberghe
Hi Jan, On 29 Jun 2013, at 17:12, Jan Vrany jan.vr...@fit.cvut.cz wrote: Hi, for 32bit application you can never allocate whole 4GB as some memory has to be reserved for kernel. The usual split is 2/2, sometimes 3/1. Plus, the actual code must be somewhere in the memory as well as the

Re: [Pharo-dev] Exploring Heap Size Limits

2013-06-29 Thread Jan Vrany
On 29/06/13 17:45, Sven Van Caekenberghe wrote: Hi Jan, On 29 Jun 2013, at 17:12, Jan Vrany jan.vr...@fit.cvut.cz wrote: Hi, for 32bit application you can never allocate whole 4GB as some memory has to be reserved for kernel. The usual split is 2/2, sometimes 3/1. Plus, the actual code must

Re: [Pharo-dev] Exploring Heap Size Limits

2013-06-29 Thread p...@highoctane.be
And at one point, even if there was free memory, things went south. [PhilMac:~/Documents/Smalltalk/2-MyWorkspaces/workspaceMemTest philippeback$] ./pharo Pharo.image memtest.st 500 1024000 errno 12 mmap failed: Cannot allocate memory [PhilMac:~/Documents/Smalltalk/2-MyWorkspaces/workspaceMemTest

Re: [Pharo-dev] Exploring Heap Size Limits

2013-06-29 Thread p...@highoctane.be
An interesting run as it is not ending by a simple OutOfMemory but with a lot of weird elements [PhilMac:~/Documents/Smalltalk/2-MyWorkspaces/workspaceMemTest philippeback$] ./pharo Pharo.image memtest.st 1200 1024000 memtest.st uptime 0h0m0s memory 25,004,456 bytes old 19,213,080 bytes

Re: [Pharo-dev] Exploring Heap Size Limits

2013-06-29 Thread p...@highoctane.be
Other than that it is possible to go quite far: [PhilMac:~/Documents/Smalltalk/2-MyWorkspaces/workspaceMemTest philippeback$] ./pharo Pharo.image memtest.st 1400 1024000 memtest.st uptime 0h0m0s memory 25,004,460 bytes old 19,212,804 bytes (76.81%) young 4,584 bytes (0.0%) used

Re: [Pharo-dev] Manage a Printer device with Semaphore forMutualExclusion

2013-06-29 Thread Stéphane Ducasse
Ciao, I work with a seaside application. I would to hear that. I wish your success. I have a printer device and i need to manage the use of it at one work at time. I think to use one Semaphore forMutualExclusion defined as variable of the specific printerTicket