[Pharo-project] Too many semaphores, image blocked

Schwab,Wilhelm K bschwab at anest.ufl.edu
Fri Oct 7 17:31:57 EDT 2011


Is there a way to save the image given that it is non-responsive?  Otherwise (and this could be "how it is") one would have to apply the fix before having the problem.  Just curious.  Should we all periodically take a semaphore head count in our images?

I try to leave a reasonable trail of backups of working images just in case I do something stupid; a little uncertainty can motivate cautious behavior...


From: pharo-project-bounces at lists.gforge.inria.fr [pharo-project-bounces at lists.gforge.inria.fr] On Behalf Of Eliot Miranda [eliot.miranda at gmail.com]
Sent: Friday, October 07, 2011 4:22 PM
To: Pharo-project at lists.gforge.inria.fr
Subject: Re: [Pharo-project] Too many semaphores, image blocked

Hi Janko,

    you need to /save/ the image having applied Smalltalk vm maxExternalSemaphoresSilently: 3000.  This must be set in the image at start-up, not after the image has loaded.  i.e. the VM inspects the value saved in the image header and applies the value *before* the image starts running.

2011/10/7 Janko Mivšek <janko.mivsek at eranova.si<mailto:janko.mivsek at eranova.si>>
Hi Henrik,

S, Henrik Sperre Johansen piše:
> On 05.10.2011 01:18, Schwab,Wilhelm K wrote:

>> The log you posted contains the string "Not enough space for external
>> objects, set a larger size at startup!"  Maybe a command-line switch
>> to the vm will give you more memory and a way to get the image going?

> Smalltalk vm maxExternalSemaphoresSilently: aSize  would be the line to
> include.
> If the script passed on a command line is higher in the startuplist than
> the InputEventSensor, it would get it working again.

Ok, I'm back having time to look at this problem and I made a start.st<http://start.st>
script below, start the image with it, but get the same blank screen as
you can see in attached screenshot. Ctrl or Alt . doesn't help.

Smalltalk vm maxExternalSemaphoresSilently: 3000

./Contents/Linux/squeak ./Contents/Resources/waste.image start.st<http://start.st>

Any more idea? Otherwise I'll start to recover from changes, but
starting this nonresponsive image would of course be faster solution:)

Best regards

Janko Mivšek
Smalltalk Web Application Server


More information about the Pharo-dev mailing list