[Vm-dev] [OpenSmalltalk/opensmalltalk-vm] GC crash on (corrupted?) image resume (#391)

Nicolas Cellier notifications at github.com
Mon Nov 11 18:16:59 UTC 2019

Could we create and publish a reproducible case (at least statistically reproducible, because it looks like heisenbug again...)? Like parsing a giant public json or something?
Is it possible to make a Squeak VM crash?
If memory got corrupted, no matter how, the bug could well be revealed at garbage collect time, when we scan the whole memory, so even if above reports indicates somehow common symptoms, it's very hard to use them as starting point for more thorough analysis of the problem...

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20191111/db8767c1/attachment.html>

More information about the Vm-dev mailing list