[Vm-dev] $x nextObject

Levente Uzonyi leves at caesar.elte.hu
Thu Jul 18 23:05:49 UTC 2019

No immediate object should ever receive #nextObject. I think the new 
immediates (Character, SmallFloat64) lack the #shouldNotImplement 
implementation. Same goes for #nextInstance.

Btw, #nextObject was obsoleted by the segmented memory model. Perhaps it 
can still answer something, but you won't be able to iterate over all 
objects with it. If that's what you want, then you should use #allObjects 


On Thu, 18 Jul 2019, Christoph Thiede wrote:

> Hello,
> is it a known bug that the Squeak VM may crash when you perform #nextObject
> on any Character object? I can reproduce this issue on multiple Windows 10
> machines, using SqueakCog 201810071412. I am familiar not at all with the VM
> implementation, but for example, after evaluating $x nextObject, the used
> RAM strongly reduces and after a few seconds, the process terminates.
> Kind regards,
> Christoph
> --
> Sent from: http://forum.world.st/Squeak-VM-f104410.html

More information about the Vm-dev mailing list