��
Do you mean seconds or minutes or more away from a crash?
��
It's doubly concerning because there is no clear way to stop the troubled process
(interrupts often bring up a debugger on something else) and because, since
one is now unable to save any code, it's unclear how to start over easily in
a new image.
Just some general ideas (you may have already considered)
The string "Diffing..." appears in only��one location in MCPatch>>initializeWithBase:target:
I'm not clear on the behaviour of�� #on:displayProgress:�� whether its possible some inside loop
can make that string appear multiple times, or whether it indicates�� #initializeWithBase:target:
is being called multiple times.
A specific check there for an escape key-combo might help debug this.
Or a class variable reset from Iceberg that halts when it exceeds a limit on the number of loops.
Or log to file five or so levels of "thisContext senders senders etc"�� for post crash analysis to help isolate the loop.
cheers -ben
P.S. While I was browsing senders-of-senders-of-senders I quickly got lost and wondered
if a tool that graphically showed a senders-tree might be a useful demo for Diagrammer.