I believe I've found a correlation: The crashes seem to have started with an instance of firefox-esr (115.11.0esr-1~deb12u1) that I was running on the side, since earlier today. Once I closed Firefox, the crashiness went away, completely.
(This is on the same laptop that needs --use-gl=egl to avoid visual artifacts, so that might have something to do with this) On Fri, 2024 May 31 15:27-04:00, Andres Salomon wrote: > > Interesting. Any chance of a backtrace (with the chromium-dbgsym > package)? I'm wondering if some (bundled) third party lib has started > requiring newer cpu extensions or something. I'm happy to provide this, but two questions: 1. In http://debug.mirrors.debian.org/debian-debug/pool/main/c/chromium/ as well as https://deb.debian.org/debian-debug/pool/main/c/chromium/, I don't see any packages with a matching version string of "125.0.6422.112-1~deb12u1" (and .141 isn't there yet). Am I missing something? 2. To get the stack trace, is the right way just running the whole thing in GDB, using "chromium -g"? Or do you set it up to make a core dump? (Sure would be nice to have an Apport-like after-the-fact workflow for this) --Daniel
