David - and anyone else that can help. Things are looking bad now!

I can now crash my VM in about 10 seconds, guaranteed. I wonder if you would
be good enough to try this on Linux. I moved your class code to another
class so I could instance the calling class and then ran this:

[1 to: 1000 do: [:a|data1 := app1 test]]fork.
[1 to: 1000 do: [:b|data2 := app2 test]]fork.
[1 to: 1000 do: [:c|data3 := app3 test]]fork.
[1 to: 1000 do: [:d|data4 := app4 test]]fork.
[1 to: 1000 do: [:e|data5 := app5 test]]fork.
[1 to: 1000 do: [:f|data6 := app6 test]]fork.
[1 to: 1000 do: [:g|data7 := app7 test]]fork.
[1 to: 1000 do: [:h|data8 := app8 test]]fork.
[1 to: 1000 do: [:i|data9 := app9 test]]fork.
[1 to: 1000 do: [:j|data10 := app10 test]]fork.

Where app1 to app10 are instances of the calling class. It breaks almost
every time (now I have taken out the Transcript writes which were slowing it
down). Maybe there are re-entrancy problems somewhere and what I am doing is
not valid. The stack trace in the dump I am pretty sure is a consequence of
where it was in the block execution and not anything to do with the crash.

Thanks
Bob

*** Confidentiality Notice *** Proprietary/Confidential
Information belonging to CGI Group Inc. and its affiliates
may be contained in this message. If you are not a recipient
indicated or intended in this message (or responsible for
delivery of this message to such person), or you think for
any reason that this message may have been addressed to you
in error, you may not use or copy or deliver this message
to anyone else.  In such case, you should destroy this
message and are asked to notify the sender by reply email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20060604/bc3b04fe/attachment.htm