On Wed, Feb 20, 2013 at 2:48 PM, Guillermo Polito <guillermopolito@gmail.com> wrote:

Yes, because the vm crash is caused by the lost of the active process...

On Wed, Feb 20, 2013 at 2:44 PM, Igor Stasenko <siguctua@gmail.com> wrote:

On 20 February 2013 14:37, Guillermo Polito <guillermopolito@gmail.com> wrote:
>
>
> On Wed, Feb 20, 2013 at 2:23 PM, Igor Stasenko <siguctua@gmail.com> wrote:
>>
>> but aside of making things work,
>> i really wonder why become on methods makes VM crash.
>> we should have an easily reproducible case for study.
>
>
> These?
>
> (Delay class>>#handleTimerEvent) setSourcePosition: 200 inFile: 1
>

this one shows "computation has terminated"
its not crashing my VM..
this happens when context has no sender to return to (sender is nil)

> (ProcessorScheduler class>>#idleProcess) setSourcePosition: 200 inFile: 1

this one crashing.. but still showing the same �"computation has
terminated" dialog before.

>
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko.
>>
>

--
Best regards,
Igor Stasenko.