Part 1 was interesting; it isn't clear why he split that into a Part 2 since it adds little to the story and is a paragraph long.

I assume the fact it is a third party application means debugging gets harder, and the business case for doing so is weaker/none.

But I would hope that some kind of reverse debugger triggered on one of these crashes would make it pretty simple to say "who wrote this 01".

	▲	microgpt an hour ago \| parent [-]
		You could also look at modules loaded into all of those processes that crashed this way.

taneq 3 hours ago | parent | prev [-]

Might have been an “I need to look into this” segueing into “ never mind”?