Hmm, at this time the app doesn't have any crush analysis feature. I need a time to learn how to implement it.
Thanks for the report.

I made a small app for it. You can enable it in settings (logger.exe will be installed and run automatically). I hope it will help to catch the cause of the crush.

I'm using latest sqlite-gui and got a crash. Where do I find any logging?

Faulting application name: sqlite-gui.exe, version: 1.9.1.0, time stamp: 0x669e6bda
Faulting module name: ntdll.dll, version: 10.0.19041.4522, time stamp: 0x8a1bb6f3
Exception code: 0xc0000374
Fault offset: 0x00000000000ff439
Faulting process id: 0x2f54
Faulting application start time: 0x01dadd5056fd85b3
Faulting application path: C:\Users\little-brother\Downloads\sqlite-gui-1.9.1-x64\sqlite-gui.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 45c6f86b-6222-4572-8d13-06058d39003a
Faulting package full name: 
Faulting package-relative application ID: 

In the app folder logger.txt if logger.exe was enabled.

The file does not exist.

:( So the cause of the crush is not related to query re-hightlighting. Only few things can be catched by the logger.
Could you provide more information about a state before crushing? How many tabs were open? Do you load any special extensions? Maybe you open a table or view/filter a resultset? Anything will be usefull.

select * from committee_summary_2024_tmp with the attached db.

test.zip

i also that after the crash, the windows clipboard is cleared out.

No custom functions and just a single tab opened.

Yeah, it's a buffer overflow. Your table has many columns and somewhere a buffer is not enought for all of them.
Thanks for the report.

Fixed.