I don't know. I don't get the errors that used to occur with the max semaphores being exceeded. I thought Igor Stasenko fixed that issue in the VM so the array that holds the semaphores grows without blocking. Or something.
What I do know is that if I 'abandon' that warning and save & quit and then reopen the image then the UI is locked and I have to use Seaside's WAScreenshot tool to suspend and resume the UI to unfreeze it. On 07/31/2013 11:57 AM, Mariano Martinez Peck wrote: > Maybe this is related to #maxExternalSemaphores: ? > > Did you try sending a large number? For my seaside images where I have > RFB I do: > > Smalltalk vm maxExternalSemaphoresSilently: 65535. > > Cheers, > > > On Wed, Jul 31, 2013 at 3:45 PM, Paul DeBruicker <pdebr...@gmail.com > <mailto:pdebr...@gmail.com>> wrote: > > Hi - > > In Pharo2 do I need to stop and start the RFB server? I 've > been > getting a > > primitive #signal in Semaphore failed > > error after the image starts. I'm using this version of RFB > > RFB-MarianoMartinezPeck.41 > > Thanks > > Paul > > > > > -- > Mariano > http://marianopeck.wordpress.com
