Comment 3 for bug 60236

I find it unlikely that the machine would have been running out of memory. The machine showing this behavior has a GiB of memory. Other software run well after firefox segfault. For example, I could browse the web with konqueror. I have tried disabling my profile my renaming ~/.mozilla, and that did not help. Even though I think this answers your questions, I will try 'free -m' and 'firefox safe-mode' when I can reproduce the bug next time. Thanks for looking into this bug.