Thanks for the additional info and for the logs Chris. So Chromium was abruptly killed, and the logs don't contain any hint as to why this might have happened.
I wonder whether this could be an out of memory situation, where the kernel decided to kill Chromium to free up memory. Could you inspect the output of `journalctl` around the timestamp when the crash occurred? In the DiskUsage section of the data attached by apport, I'm seeing that your /home partition is almost full (63M free out of 32GB), maybe that could explain this sort of abrupt termination if Chromium is trying to write profile or cache data to disk? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960313 Title: [snap] chromium crashes regularly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1960313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
