User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:41.0) Gecko/20100101 Firefox/41.0 Build ID: 20150817163452 Steps to reproduce: Since transferring my data and user profiles to a newer MacBook Pro 6.2 with OSX 10.8.5 and 4 GB RAM, I am getting crashes multiple times a day. I have tried: - starting with add-ons off - safe mode - resetting Firefox - switching to FF Beta 41 latest version No change with any of these. I am running on average 13 windows each with 5-10 tabs as I have for years. This same profile was generally stable on my prior MB Pro 1.1 with OSX 10.6.8 and 2 GB RAM. Other symptoms: FF is using crazy amount of RAM, 1.1 to over 1.5 GB and over time the inactive RAM climbs steadily up to around 1.5 GB, leaving very little free RAM, as though FF is not giving memory back to the system properly. The extension Tab Memory Usage doesn't show tabs to be using anything near the total being used, most are 20 MB or even way less than 1 MB. Actual results: Crash reports: Report ID Date Submitted bp-dc9f00c8-2acd-4874-99ff-d28a22150821 8/20/15 9:28 PM bp-5b670e57-f333-48c3-b694-728c22150820 8/20/15 6:50 PM bp-51779829-c444-439b-998c-0e1562150820 8/19/15 8:31 PM bp-fad72061-2522-4bf9-93f1-9df0e2150819 8/19/15 10:08 AM bp-1ed8051a-4d8e-42f2-9aad-a19552150819 8/18/15 9:52 PM bp-b76ea08d-ed6d-444b-a4e5-258c02150818 8/18/15 5:03 PM bp-de534e43-0498-459d-a6d9-0fb582150818 8/18/15 3:18 PM bp-a4dfabce-5c82-4acb-aa85-2ad492150818 8/18/15 11:34 AM bp-99b22bc9-6c8b-42ed-8c7c-7e5262150815 8/15/15 2:37 PM bp-ce19eeab-0723-4172-9725-49ce12150815 8/15/15 12:27 PM bp-6457dfb0-ecd3-4f30-b112-c6a3c2150814 8/14/15 5:24 PM bp-1e5a86fd-00f6-41d5-bf7c-020742150814 8/14/15 5:02 PM Two of them are titled "@ @0x0 | mozilla::dom::DeferredFinalizerImpl<T>::DeferredFinalize(unsigned int, void*)" and 1 is "@ js::jit::AssemblerX86Shared::bind(js::jit::Label*)" but neither of those match the other symptoms or my system that I can find. All three of those have EXC_BAD_ACCESS as the crash reason. I am attaching a JPG of Activity Monitor. Expected results: FF should have run stably and not crashed.

Some of theses crashes are already reported, see bug 1124397 and bug 1192823.

Steven, can the reporter here help with troubleshooting bug 1124397 in any way? > Report ID Date Submitted > bp-dc9f00c8-2acd-4874-99ff-d28a22150821 8/20/15 9:28 PM 41.0b2 [@ js::jit::AssemblerX86Shared::bind(js::jit::Label*) ] > bp-5b670e57-f333-48c3-b694-728c22150820 8/20/15 6:50 PM 41.0b2 [@ js::jit::AssemblerX86Shared::bind(js::jit::Label*) ] > bp-51779829-c444-439b-998c-0e1562150820 8/19/15 8:31 PM 40.0 [@ mozilla::dom::DeferredFinalizerImpl<T>::DeferredFinalize(unsigned int, void*) ] > bp-fad72061-2522-4bf9-93f1-9df0e2150819 8/19/15 10:08 AM 40.0 [@ @0x0 | mozilla::dom::DeferredFinalizerImpl<T>::DeferredFinalize(unsigned int, void*) ] > bp-1ed8051a-4d8e-42f2-9aad-a19552150819 8/18/15 9:52 PM 40.0 [@ js::jit::AssemblerX86Shared::bind(js::jit::Label*) ] > bp-b76ea08d-ed6d-444b-a4e5-258c02150818 8/18/15 5:03 PM 40.0 [@ js::jit::AssemblerX86Shared::bind(js::jit::Label*) ] w/extensions > bp-de534e43-0498-459d-a6d9-0fb582150818 8/18/15 3:18 PM 40.0 [@ AddClassInfo ] w/extensions > bp-a4dfabce-5c82-4acb-aa85-2ad492150818 8/18/15 11:34 AM 40.0 [@ mozilla::dom::DeferredFinalizerImpl<T>::DeferredFinalize(unsigned int, void*) ] > bp-99b22bc9-6c8b-42ed-8c7c-7e5262150815 8/15/15 2:37 PM 40.0 [@ nsUrlClassifierPrefixSet::SetPrefixes(unsigned int const*, unsigned int) ] w/extensions > bp-ce19eeab-0723-4172-9725-49ce12150815 8/15/15 12:27 PM 40.0 [@ mozilla::dom::DeferredFinalizerImpl<T>::DeferredFinalize(unsigned int, void*) ] > bp-6457dfb0-ecd3-4f30-b112-c6a3c2150814 8/14/15 5:24 PM 40.0 [@ shutdownhang | libsystem_kernel.dylib@0x120fa ] w/extensions > bp-1e5a86fd-00f6-41d5-bf7c-020742150814 8/14/15 5:02 PM 40.0 [@ mozalloc_abort(char const*) | Abort | NS_DebugBreak | nsDebugImpl::Abort(char const*, int) ]

(In reply to Nickolay_Ponomarev from comment #2) > Steven, can the reporter here help with troubleshooting bug 1124397 in any > way? > > > Report ID Date Submitted > > bp-dc9f00c8-2acd-4874-99ff-d28a22150821 8/20/15 9:28 PM 41.0b2 [@ js::jit::AssemblerX86Shared::bind(js::jit::Label*) ] > > bp-5b670e57-f333-48c3-b694-728c22150820 8/20/15 6:50 PM 41.0b2 [@ js::jit::AssemblerX86Shared::bind(js::jit::Label*) ] > > bp-51779829-c444-439b-998c-0e1562150820 8/19/15 8:31 PM 40.0 [@ mozilla::dom::DeferredFinalizerImpl<T>::DeferredFinalize(unsigned int, void*) ] > > bp-fad72061-2522-4bf9-93f1-9df0e2150819 8/19/15 10:08 AM 40.0 [@ @0x0 | mozilla::dom::DeferredFinalizerImpl<T>::DeferredFinalize(unsigned int, void*) ] > > bp-1ed8051a-4d8e-42f2-9aad-a19552150819 8/18/15 9:52 PM 40.0 [@ js::jit::AssemblerX86Shared::bind(js::jit::Label*) ] > > bp-b76ea08d-ed6d-444b-a4e5-258c02150818 8/18/15 5:03 PM 40.0 [@ js::jit::AssemblerX86Shared::bind(js::jit::Label*) ] w/extensions > > bp-de534e43-0498-459d-a6d9-0fb582150818 8/18/15 3:18 PM 40.0 [@ AddClassInfo ] w/extensions > > bp-a4dfabce-5c82-4acb-aa85-2ad492150818 8/18/15 11:34 AM 40.0 [@ mozilla::dom::DeferredFinalizerImpl<T>::DeferredFinalize(unsigned int, void*) ] > > bp-99b22bc9-6c8b-42ed-8c7c-7e5262150815 8/15/15 2:37 PM 40.0 [@ nsUrlClassifierPrefixSet::SetPrefixes(unsigned int const*, unsigned int) ] w/extensions > > bp-ce19eeab-0723-4172-9725-49ce12150815 8/15/15 12:27 PM 40.0 [@ mozilla::dom::DeferredFinalizerImpl<T>::DeferredFinalize(unsigned int, void*) ] > > bp-6457dfb0-ecd3-4f30-b112-c6a3c2150814 8/14/15 5:24 PM 40.0 [@ shutdownhang | libsystem_kernel.dylib@0x120fa ] w/extensions > > bp-1e5a86fd-00f6-41d5-bf7c-020742150814 8/14/15 5:02 PM 40.0 [@ mozalloc_abort(char const*) | Abort | NS_DebugBreak | nsDebugImpl::Abort(char const*, int) ] How can I help? I am not a coder myself, just a user.

All, Per a response I received on the Mozilla Support Forum, this turns out to be caused (at least in part) by an interaction with MS Office Mac. There IS a workaround I found by Googling the bug: running Firefox in 32 bit mode. I closed FF, went to the application in my Applications folder, right-clicked on it, selected "Get Info" and checked the "run in 32-bit mode" option box. Haven't crashed since doing this with either error. Obviously, there IS still a bug somewhere but it may be caused by Microsoft. Best wishes, David PS: I posted this to the second bug mentioned in the first response to my report. Should it get posted to 1124397 as well?

> Steven, can the reporter here help with troubleshooting bug 1124397 in any way? Yes. David, can you run the following build for a day and report the crash ids for the crashes that happen with it? It's a tryserver build made with my debug logging patch for bug 1124397 -- it adds extra information to crash reports concerning that bug's crashes. http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/smichaud@pobox.com-1cf744fe1b7c/try-macosx64/firefox-43.0a1.en-US.mac.dmg

(In reply to David Butler from comment #4) > All, > > Per a response I received on the Mozilla Support Forum, this turns out to be > caused (at least in part) by an interaction with MS Office Mac. There IS a > workaround I found by Googling the bug: running Firefox in 32 bit mode. Do you have a URL reference for this? Unfortunately smichaud's try build is expired, and he is also Retired

> Unfortunately smichaud's try build is expired I'd be willing to do another tryserver build. But I no longer have access to the information it would write to the Socorro crash logs -- so there'd be no point.

Hi, Marking this as Resolved: Incomplete due to the lack of response from the reporter. Reporter, please feel free to reopen it if you are still having this issue.

ovidiu boca, please also remove needinfoS when closing bug. smichaud, FWIW I am able to access crash-stats private data. So if the reporter returns and still sees the problem ...

> Do you have a URL reference for this? FWIW, I couldn't find it, but there's a new support thread with very similar crashes: https://support.mozilla.org/en-US/questions/1111080 David, if you have any updates on this, it might help. Do you still run Firefox in 32-bit mode and without further js::jit::AssemblerX86Shared::bind or mozilla::dom::DeferredFinalizerImpl crashes? I couldn't find any information that confirms the MS Office for Mac hypothesis; it might be a misunderstanding: looks like something is mis-attributing system libraries like libsystem_kernel.dylib to "Word for Mac" - https://www.google.com/search?q=libsystem_kernel.dylib+%22Word+for+Mac%22+inurl%3Asupport.mozilla.org%2Fquestions