[Vm-dev] Socket's readSemaphore is losing signals with Cog on
Henrik Sperre Johansen
henrik.s.johansen at veloxit.no
Mon Aug 15 21:14:15 UTC 2011
On 15.08.2011 19:14, Colin Putney wrote:
> On Sun, Aug 14, 2011 at 12:44 PM, Levente Uzonyi<leves at elte.hu> wrote:
>> So I'm pretty sure this bug is Cog specific. Reproducing it seems to be
>> pretty hard, so a code review (with sufficient knowledge :)) is more likely
>> to help solving this issue.
> FWIW, I can reproduce it fairly easily using the Xtreams test suite.
> Running XTSocketReadingWritingTest almost always has several tests
> time out because of it.
FWIW, I ran the XTSocketReadingWritingTest often enough to see errors in
the results, and interrupted it while it looked to be hanging (this in
In latest Pharo images, I got the "'Not enough space for external
objects, set a larger size at startup!'" error message I added for
trying to adjust ExternalSemaphoreTable size at runtime.
If default behaviour in your image is to just silently increase size/not
increase it at all, that may explain the lost signals.
More information about the Vm-dev