Could you add the http link you have visited when FF crashed? Maybe someone can reproduce it.
Does your FF also crash with apparmor profile disabled? My experience is that FF tolerates a lot of these apparmor-blocked actions which are reported in syslog. These logged errors are not necessarily the reason why FF crashed. But could, of course. In your case, I would also check the system memory with mem86. Let it run during a weekend and see what happens. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1656065 Title: Firefox and plugin-container (Chrome_ChildThr): segfault at 0 ip b76df673 sp b1efe9f0 error 6 in plugin-container/libxul.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1656065/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs