How to track down why firefox is crashing so much.

Jesse Ruderman jruderman at gmail.com
Fri Nov 22 21:40:37 UTC 2013


https://developer.mozilla.org/en-US/docs/Building_Firefox_with_Address_Sanitizer
explains where you can download ASan builds for Linux, and how you can
build your own for Linux or Mac OS X. The instructions should work on
Mac OS X 10.8 and I just updated them to work on 10.9. You might need
to add "-mllvm -asan-stack=0" to your mozconfig C*FLAGS to work around
https://bugzilla.mozilla.org/show_bug.cgi?id=935795.

I can help you on IRC if you run into trouble or want help
interpreting a stack trace. (I'm Jesse in #security and #memshrink.)

On Fri, Nov 22, 2013 at 1:16 PM, Casey Jordan <casey.jordan at jorsek.com> wrote:
> mccr8 Didn't think it was an oom exception.
>
> Here is another one that I just reproduced, it seems similar but different:
>
> https://crash-stats.mozilla.com/report/index/cf9e46e8-f94e-4019-99c5-d1f7b2131122
>
>
> On Fri, Nov 22, 2013 at 3:40 PM, Casey Jordan <casey.jordan at jorsek.com>
> wrote:
>>
>> Thanks Jesse,
>>
>> I doubt that my machine is running out of memory since I have 16GB of it
>> and most of that is free at any given time. I will try and investigate the
>> other possibilities.
>>
>> Where do I get this "address sanitizer build"?
>>
>> Thanks again for the feedback!
>>
>>
>> On Fri, Nov 22, 2013 at 3:02 PM, Jesse Ruderman <jruderman at gmail.com>
>> wrote:
>>>
>>> Most of the crashes in your first block look like out-of-memory
>>> crashes. Many of them even have mozalloc_handle_oom in the signature.
>>>
>>> I thought OOM crashes didn't happen in 64-bit builds like the one
>>> you're using. So that's weird.  Are you somehow out of both RAM and
>>> swap? Is that a thing that can even happen on Mac?
>>>
>>> I guess it's also possible that you're hitting memory corruption
>>> that's being interpreted as out-of-memory. Given that you're using
>>> poorly-tested platform features (XSLT, XPath), it wouldn't be too
>>> surprising if you have stumbled on a memory corruption bug. You could
>>> try running an address-sanitizer build (2-3x slowdown) to find out
>>> whether that's the case.
>>>
>>> Your last crash is in the cycle collector. mccr8 in #memshrink
>>> (irc.mozilla.org) could tell you whether the cycle collector crash is
>>> likely to be a result of running out of memory or a distinct bug.
>>
>>
>>
>>
>> --
>> --
>> Casey Jordan
>> easyDITA a product of Jorsek LLC
>> "CaseyDJordan" on LinkedIn, Twitter & Facebook
>> (585) 348 7399
>> easydita.com
>>
>>
>> This message is intended only for the use of the Addressee(s) and may
>> contain information that is privileged, confidential, and/or exempt from
>> disclosure under applicable law.  If you are not the intended recipient,
>> please be advised that any disclosure  copying, distribution, or use of
>> the information contained herein is prohibited.  If you have received
>> this communication in error, please destroy all copies of the message,
>> whether in electronic or hard copy format, as well as attachments, and
>> immediately contact the sender by replying to this e-mail or by phone.
>> Thank you.
>
>
>
>
> --
> --
> Casey Jordan
> easyDITA a product of Jorsek LLC
> "CaseyDJordan" on LinkedIn, Twitter & Facebook
> (585) 348 7399
> easydita.com
>
>
> This message is intended only for the use of the Addressee(s) and may
> contain information that is privileged, confidential, and/or exempt from
> disclosure under applicable law.  If you are not the intended recipient,
> please be advised that any disclosure  copying, distribution, or use of
> the information contained herein is prohibited.  If you have received
> this communication in error, please destroy all copies of the message,
> whether in electronic or hard copy format, as well as attachments, and
> immediately contact the sender by replying to this e-mail or by phone.
> Thank you.



More information about the firefox-dev mailing list