Hi Eliot --
From the top of my hat, here are things that might help finding the cause of that slowdown:
1. No stepping is involved in the debugger itself. Neither the outer model (Debugger) nor its embedded inspectors will receive a stepping call from Morphic. See Debugger >> #wantsStepsIn:.
2. Some direct stepping is involved in the debugger's text fields via TextMorph >> #onBlinkCursor. That can be turned off via: "Editor blinkingCursor: false". Existing text fields are not updated immediately, but there is code for that in PreferenceWizardMorph
>> #toggleBlinkingCursor.
3. Syntax highlighting is updated on every code change, not selection change. Try disabling such highlights via "SHTextStylerST80 syntaxHighlightingAsYouType: false.". Existing text fields are updated automatically.
4. We chose to make URL highlighting work on mouse-move events. This may slow down your interactions with debugger text. Try removing the call to #mouseEnterOnTextAction: from TextMorph >> #mouseMove:.
5. For Trunk via Morphic-mt.2152, I just added "spy on action invocation" to each button's debug menu, which is accessible via the Morphic halo. This can help to better understand the slow-down in your image.
It seems very strange that a click on "step into" or "step over" takes many seconds... you can also use the halo to inspect the debugger's model to then evaluate: "MessageTally spyOn: [self stepInto]" or #stepOver or #stepThrough.
Hope this helps! Happy Squeaking :-)
Best,
Marcel
Am 13.02.2024 02:32:47 schrieb Eliot Miranda <eliot.miranda@gmail.com>:
Hi All,
I'm trying to debug an inlining edge case in the VM for the threaded VM that Leon is doing. The debugger is unusably slow (steps taking 10 seconds, etc). I've raised this issue before but was brushed off.
I suspect somewhere in the new (last two years?) highlighting code is taking a lot of time. Would the author(s) please provide me with some snippets of code i can use to try and measure performance? And/or would anybody be willing to pair (I'm on PST) in
trying to get to the bottom of this? It's extremely frustrating to try and work when the debugger is unusable.