narrowwindow

Overview ¶

Command narrowwindow runs the 77 milliseconds the corruption happens in, over and over, and says what got damaged.

⛔⛔ THE JOURNAL NAMED THE WINDOW AND IT IS SMALL. On 2026-09-27 an ordinary launch read three strings correctly from a clean settings file and found them with their first four bytes zeroed 77 ms later:

15:22:00.650  journal opened
15:22:00.669  permissions
15:22:00.713  the menu bar item is built, with 15 rows
15:22:00.724  the menu draws 17 key equivalents from 40 granted shortcuts
15:22:00.727  no display matches "\x00\x00\x00\x00RE Beast"

Between the clean read and the damaged use there is nothing but the permission check and the menu bar. No virtual display had been made -- which retires the framing the hunt ran on for three weeks, that the fault depends on how many virtual displays exist.

⭐⭐ AND THIS IS THE FIRST BENCH THAT IS SAFE TO LOOP ON A WORKING MACHINE. Every earlier one made virtual displays, which froze the author's Mac twice. This one makes a menu bar item and reads a file. Nothing else. So it can run two hundred times in a minute on the machine where the fault actually appears, which is the one thing this hunt has never been able to do.

It watches BOTH: the witnesses, which say what shape of object is hit, and the strings from the settings file, which are the objects actually known to have been hit.