Re: [Pharo-project] Too many semaphores, image blocked
On 21.10.2011 10:42, Henrik Sperre Johansen wrote:
On 20.10.2011 15:30, Igor Stasenko wrote:
2011/10/20 Janko Mivšek<janko.mivsek@eranova.si>:
Hi guys,
I'm measuring how my image is breathing through the time and what is interesting is how nr. of Semaphore instances is variating through the time. Every hour just before snapshot I report nr of instances, see last 10 hours:
Well, the number of semaphores tells nothing because not all of them serve for sockets.
There are 3 semaphores per socket. So, if you have 4 sockets, there should be 12 external objects. Of course not counting others, which is there for other purposes.
Could you add following to report:
Socket registry size StandardFileStream registry size (ExternalSemaphoreTable unprotectedExternalObjects reject: #isNil) size There's something wrong with startup/shutdown list, at least with my Pharo 1.4 image... Both InputEventFetcher and InputEventPollingFetcher are in the lists, going back to at least 1.3 Can't have that. Probably got there when switching InputFetcher (IE a _long_ time ago) due to being careless with receiver of #install / #deinstall... InputEventPollingFetcher should be removed.
Cheers, Henry
On 21 October 2011 10:59, Henrik Sperre Johansen <henrik.s.johansen@veloxit.no> wrote:
On 21.10.2011 10:42, Henrik Sperre Johansen wrote:
On 20.10.2011 15:30, Igor Stasenko wrote:
2011/10/20 Janko Mivšek<janko.mivsek@eranova.si>:
Hi guys,
I'm measuring how my image is breathing through the time and what is interesting is how nr. of Semaphore instances is variating through the time. Every hour just before snapshot I report nr of instances, see last 10 hours:
Well, the number of semaphores tells nothing because not all of them serve for sockets.
There are 3 semaphores per socket. So, if you have 4 sockets, there should be 12 external objects. Of course not counting others, which is there for other purposes.
Could you add following to report:
Socket registry size StandardFileStream registry size (ExternalSemaphoreTable unprotectedExternalObjects reject: #isNil) size
There's something wrong with startup/shutdown list, at least with my Pharo 1.4 image...
Both InputEventFetcher and InputEventPollingFetcher are in the lists, going back to at least 1.3 Can't have that. Probably got there when switching InputFetcher (IE a _long_ time ago) due to being careless with receiver of #install / #deinstall... InputEventPollingFetcher should be removed.
Yes.
Cheers, Henry
-- Best regards, Igor Stasenko.
S, Henrik Sperre Johansen piše:
There's something wrong with startup/shutdown list, at least with my Pharo 1.4 image... Both InputEventFetcher and InputEventPollingFetcher are in the lists, going back to at least 1.3 Can't have that. Probably got there when switching InputFetcher (IE a _long_ time ago) due to being careless with receiver of #install / #deinstall...
InputEventPollingFetcher should be removed.
Henrik, can you prepare a patch (or instructions how to remove it) so that I'll check immediately? Best regards Janko -- Janko Mivšek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si
On 21. okt. 2011, at 16:56, Janko Mivšek <janko.mivsek@eranova.si> wrote:
S, Henrik Sperre Johansen piše:
There's something wrong with startup/shutdown list, at least with my Pharo 1.4 image... Both InputEventFetcher and InputEventPollingFetcher are in the lists, going back to at least 1.3 Can't have that. Probably got there when switching InputFetcher (IE a _long_ time ago) due to being careless with receiver of #install / #deinstall...
InputEventPollingFetcher should be removed.
Henrik, can you prepare a patch (or instructions how to remove it) so that I'll check immediately?
Best regards Janko
Execute something like: Smalltalk removeFromStartUpList: InputEventPollingFetcher; removeFromShutDownList: InputEventPollingFetcher. In a workspace, and you should be good to go. Cheers, Henry
participants (4)
-
Henrik Johansen -
Henrik Sperre Johansen
-
Igor Stasenko -
Janko Mivšek