On 5/31/24 15:51, Daniel Richard G. wrote:
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?
I'm going from memory here, but I believe the dak installation on security.debian.org doesn't keep dbgsym packages for historical reasons. Thus, they're only available once chromium gets moved to stable-proposed-updates. https://tracker.debian.org/pkg/chromium shows .60 as being the last one in stable-p-u. At some point in the next week or two, someone from the release team will likely accept the newer chromium packages into stable-p-u, at which point the dbgsym packages for .141 (or whatever the latest version is) will be available.
It sucks, but it is what it is. You could either spend a bunch of time building chromium for the dbgsym packages, or I could put my local build of .141 online w/ dbgsym packages for you to try out (assuming amd64?), or you could downgrade to .60 and use those dbgsym packages.
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)
Yes, just running 'chromium -g' will launch it inside gdb; you may have to manually type 'run' to start it inside gdb, I forget. But then you'll get a backtrace (or you can ctrl-c and run 'bt', if it's a deadlock or something). I haven't bothered w/ core dumps of chromium before, so I can't speak to that.
OpenPGP_signature.asc
Description: OpenPGP digital signature
