Hi Alex,
�� �� I think Marcus is right.�� The run:with:in: mechanism is invoked when the VM looks up a message and finds something other than a CompiledMethod in the relevant method dictionary as the value of the selector.�� Occasionally this can happen from stack corruption, otherwise it implies method dictionary corruption.�� Either could be caused by an FFI bug, a VM bug, etc.�� Do you have the image still live?�� We could meet on Slack and i could perhaps use lldb to look at the stack.�� If not, the approach would be to find a reproducible case (painful, given that you're trying to get work done and save it) and then run the reproducible case with assertions and heap leak checking turned on to try and catch the error as early as possible.
Forgive me, but may I beg you to post the text of stack back traces in future not screenshots?�� The screenshots have two major disadvantages; a) they're huge and b) one cannot search email messages for the text they contain.�� You can use e.g. shell level tools to copy the text, eg from the terminal or from the console.
Hello,
When saving one of the latest pharo70 image I got an infinite recursion loop due to message not understood. Force closing it probably lead to image corruption and it became un-openable anymore. Any idea what is going on? It does not look like a unique case because there are a few pharo70 images that already died in front of me...
VM: Mac OS - x64 - 1013.5 - CoInterpreter VMMaker.oscog-eem.2461 uuid: b3cd33f5-6309-43a1-b669-7a1805111f34 Oct 31 2018
StackToRegisterMappingCogit VMMaker.oscog-eem.2464 uuid: 0b1fa0a3-a781-4fd5-b1cf-1809796ccbbf Oct 31 2018
VM: 201810311808 https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Wed Oct 31 11:08:29 2018 CommitHash: c7a9b1f Plugins: 201810311808 https://github.com/OpenSmalltalk/opensmalltalk-vm.git
Image: Pharo7.0.0alpha [Build information: Pharo-7.0.0+alpha.build.1361.sha.011b7c939adeb52338baad16a694cab2e7a54d74 (64 Bit)]
--