It's possible, but unlikely, that we've pushed a "pre-apply damage" job to the renderer thread queue (or that we've pushed it, and that a thread is now working on it) when we shutdown a terminal instance.
This is sometimes caught in an assertion in term_destroy(), where we check the queue length is 0. Other times, or in release builds, we might crash in the thread, or in the shutdown logic when freeing the buffer chains associated with the terminal instance.
Fix by ensuring there's no pre-apply damage operation queued, or running, before shutting down a terminal instance.
Closes #2263
It's possible, but unlikely, that we've pushed a "pre-apply damage" job to the renderer thread queue (or that we've pushed it, and that a thread is now working on it) when we shutdown a terminal instance.
This is sometimes caught in an assertion in `term_destroy()`, where we check the queue length is 0. Other times, or in release builds, we might crash in the thread, or in the shutdown logic when freeing the buffer chains associated with the terminal instance.
Fix by ensuring there's no pre-apply damage operation queued, or running, before shutting down a terminal instance.
Closes #2263