This is not an out of memory crash. This is a code bug in firefox and/or in the shared library being called by firefox. Usually this is related to something unexpected/unhandled in the data stream being processed incorrectly. I have had a few of these firefox crashes since around Nov 20. Hopefully someone fixes it soon. On Sun, Dec 10, 2023 at 5:00 AM Patrick O'Callaghan <pocallaghan@xxxxxxxxx> wrote: > > This morning I found this in my journal: > > Dec 09 23:53:04 Bree kernel: traps: Isolated Web Co[188480] general protection fault ip:7f6a44c75871 sp:7ffc2a7be1f0 error:0 in libxul.so[7f6a42462000+4664000] > Dec 09 23:53:04 Bree systemd[1]: Started systemd-coredump@12-239925-0.service - Process Core Dump (PID 239925/UID 0). > Dec 09 23:53:05 Bree abrt-dump-journal-oops[182510]: abrt-dump-journal-oops: Found oopses: 1 > Dec 09 23:53:05 Bree abrt-dump-journal-oops[182510]: abrt-dump-journal-oops: Creating problem directories > Dec 09 23:53:06 Bree abrt-dump-journal-oops[182510]: Reported 1 kernel oopses to Abrt > Dec 09 23:53:07 Bree abrt-server[239927]: Can't find a meaningful backtrace for hashing in '.' > Dec 09 23:53:07 Bree abrt-server[239927]: Deleting non-reportable oops '.' because DropNotReportableOopses is set to 'yes' > Dec 09 23:53:07 Bree abrt-server[239927]: 'post-create' on '/var/spool/abrt/oops-2023-12-09-23:53:05-182510-0' exited with 1 > Dec 09 23:53:07 Bree abrt-server[239927]: Deleting problem directory '/var/spool/abrt/oops-2023-12-09-23:53:05-182510-0' > Dec 09 23:53:07 Bree abrt-server[239927]: Lock file '.lock' was locked by process 239940, but it crashed? > Dec 09 23:53:07 Bree systemd-coredump[239926]: [🡕] Process 188480 (Isolated Web Co) of user 1000 dumped core. > > Module libxcb-dri3.so.0 from rpm libxcb-1.13.1-12.fc39.x86_64 > Module libnuma.so.1 from rpm numactl-2.0.16-3.fc39.x86_64 > Module libogg.so.0 from rpm libogg-1.3.5-6.fc39.x86_64 > > etc. etc. (I'll omit the rest of the trace) > > libxul.so is part of Firefox (and Thunderbird, which I don't use). > Apparently "Isolated Web Co" is a Firefox process which has been > reported for years as leaking memory, though I haven't noticed it doing > this myself (I have a lot of swap). Some people think it's related to > viewing YouTube videos, which I do do. > > My question is: why doesn't the OOM killer stamp on this before it gets > out of hand? Isn't that what it's for? > > poc > -- > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
