I believe it was this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1279574 https://bugs.chromium.org/p/chromium/issues/detail?id=127957... I en

I believe it was this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1279574 https://bugs.chromium.org/p/chromium/issues/detail?id=127957... I encountered it when I updated a bunch of NixOS packages at once. Since the crash happened in chromium, I figured I'd downgrade that specific package by pinning an older channel. It still didn't work. But I knew that chromium had worked before, and nix doesn't really use the FHS, so the system wouldn't be polluted with random versions of packages. I also knew that the SHA for chromium had to match what was here: https://github.com/NixOS/nixpkgs/commit/a1c5e5bc40749652503cd956e777455e2180b663 https://github.com/NixOS/nixpkgs/commit/a1c5e5bc40749652503c.... So if chromium wasn't the issue, the problem would have to lie elsewhere. Comparing the last two generations of my system, I found that Sway had updated, which also brought a new version of wlroots that broke older versions of chromium. I eventually found my way to this issue and rolled Sway back until the fix landed in stable. There were probably easier/quicker ways to reach the same conclusion I did. But I think that knowing the software on my system was built correctly, and was relatively isolated (i.e. wasn't depending on random versions of libraries in the FHS) made it so I wouldn't fall down a rabbit hole that lead to a dead end.