<div id="__MailbirdStyleContent" style="font-size: 10pt;font-family: Arial;color: #000000;text-align: left" dir="ltr">
<div>Hi Lauren --<br></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">> The .1 is the debugger upon entry into MVC.</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">Hmm... the list of submorphs seems to include a "nil" here:</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">...</span></div><div><span style="font-size: 13.3333px">UndefinedObject(Object)>>doesNotUnderstand: #ownerChanged</span></div><div><span style="font-size: 13.3333px">[] in PluggableTextMorphPlus(Morph)>>doLayoutIn:</span></div><div><span style="font-size: 13.3333px">...</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">Which is then #pass 'ed on in #doLayoutSafely because the receiver in question is not a morph but nil and thus cannot be found on the stack:</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">...</span></div><div><span style="font-size: 13.3333px">MessageNotUnderstood(Exception)>>pass</span></div><div><span style="font-size: 13.3333px">[] in [] in PluggableTextMorphPlus(Morph)>>doLayoutSafely</span></div><div><span style="font-size: 13.3333px">...</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">What I do not understand is why this simple incident counts as a recursive error:</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">...</span></div><div><span style="font-size: 13.3333px">ToolSet class>>handleRecursiveError:</span></div><div><span style="font-size: 13.3333px">Debugger class>>openOn:context:label:contents:fullView:</span></div><div><span style="font-size: 13.3333px">...</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">But then I look at the bottom-most portion of the stack you shared:</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">...</span></div><div><span style="font-size: 13.3333px">PasteUpMorph>>privateOuterDisplayWorld</span></div><div><span style="font-size: 13.3333px">PasteUpMorph>>displayWorld</span></div><div><span style="font-size: 13.3333px">[] in MorphicDebugger class>>openOn:context:label:contents:fullView:</span></div><div><span style="font-size: 13.3333px">-- and more not shown --</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">So we were already trying to open a debugger but failed in layouting an instance of PluggableTextMorphPlus, which has a submorph that was "nil" instead of a morph, which in turn does not understand #ownerChanged.</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">Yes, that is a recursive error. Debuggers need to rely on scrollable list and text fields to work. But why is that instance of PluggableTextMorphPlus broken in the first place? Hmm....</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">> The .2 is attempting to create a new morphic project.</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">Aha! This here is a rather recent change where we wanted to see the world docking bar in the project's thumbnail before entering the project for the first time:</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">PluggableTextView(Object)>>doesNotUnderstand: #name:</span></div><div><span style="font-size: 13.3333px">SearchBar>>buildWith:</span></div><div><span style="font-size: 13.3333px">MVCToolBuilder(ToolBuilder)>>build:</span></div><div><span style="font-size: 13.3333px">ToolBuilder class>>build:</span></div><div><span style="font-size: 13.3333px">SearchBar class>>build</span></div><div><span style="font-size: 13.3333px">TheWorldMainDockingBar>>searchBarOn:</span></div><div><span style="font-size: 13.3333px">TheWorldMainDockingBar>>rightSideOn:</span></div><div><span style="font-size: 13.3333px">TheWorldMainDockingBar>>fillDockingBar:</span></div><div><span style="font-size: 13.3333px">TheWorldMainDockingBar>>createDockingBar</span></div><div><span style="font-size: 13.3333px">MorphicProject>>createOrUpdateMainDockingBar</span></div><div><span style="font-size: 13.3333px">MorphicProject>>assureMainDockingBarPresenceMatchesPreference</span></div><div><span style="font-size: 13.3333px">MorphicProject>>initialize</span></div><div><span style="font-size: 13.3333px">...</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">So, I think I will guard this #assureMainDockingBarPresenceMatchesPreference for now until we can find a way to safely do stuff for other projects. Well, things like "ToolBuilder default" might have to be a dynamically-scoped variable after all. We should think about this after the release.</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">***</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">Thanks for the report!</span></div><div><span style="font-size: 13.3333px"><br></span></div><div><span style="font-size: 13.3333px">Best,</span></div><div><span style="font-size: 13.3333px">Marcel</span></div><div class="mb_sig"></div>
<blockquote class="history_container" type="cite" style="border-left-style: solid;border-width: 1px;margin-top: 20px;margin-left: 0px;padding-left: 10px;min-width: 500px">
<p style="color: #AAAAAA; margin-top: 10px;">Am 22.01.2022 08:16:22 schrieb Lauren Pullen <drurowin@gmail.com>:</p><div style="font-family:Arial,Helvetica,sans-serif">Hi list,
<br>
<br>I was running the Test Runner on packages pulled in by checking the
<br>bonus options at the end of the preference wizard and the home project
<br>aborted. I didn't land in the emergency evaluator, only the MVC root
<br>project.
<br>
<br>There are two logs I took:
<br>
<br>The .1 is the debugger upon entry into MVC.
<br>
<br>The .2 is attempting to create a new morphic project.
<br>
<br>I also saved the image, one right before running the test runner and one
<br>after morphic quit. I restarted the before-image to see what test
<br>produced the crash and was unable to reproduce it.
<br><br></div></blockquote></div>