Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

Firefox Aurora crashing upon opening after update

more options

I'm running Aurora 32.0a2. This morning I updated Aurora when the little popup said there was a new update available. Since then, I haven't been able to open Aurora. It crashes every time I do, even in Safemode. Sometimes I can manage to get Aurora to open, but when I try to go to a webpage (doesn't matter which), it crashes again. The Mozilla Crash Reporter comes up and asks me if I want to send a report, then it asks if I want to restart or restart in Safemode. No matter what I do, it crashes. Here are the latest reports:

bp-fa372646-76a6-4557-9359-a3cce2140628 bp-f946dafa-7f6b-4e34-be02-d51d72140628 bp-4a53ee5e-aae5-4bd0-9b3c-df39d2140628 bp-d32ea2ff-c7d1-485e-9af6-b537a2140628 bp-c9f86601-f247-493a-a3a6-b91d32140628

Thanks, Urbancowgurl777

I'm running Aurora 32.0a2. This morning I updated Aurora when the little popup said there was a new update available. Since then, I haven't been able to open Aurora. It crashes every time I do, even in Safemode. Sometimes I can manage to get Aurora to open, but when I try to go to a webpage (doesn't matter which), it crashes again. The Mozilla Crash Reporter comes up and asks me if I want to send a report, then it asks if I want to restart or restart in Safemode. No matter what I do, it crashes. Here are the latest reports: bp-fa372646-76a6-4557-9359-a3cce2140628 bp-f946dafa-7f6b-4e34-be02-d51d72140628 bp-4a53ee5e-aae5-4bd0-9b3c-df39d2140628 bp-d32ea2ff-c7d1-485e-9af6-b537a2140628 bp-c9f86601-f247-493a-a3a6-b91d32140628 Thanks, Urbancowgurl777

Valgt løsning

See also:

  • bug 1031697 - Aurora32.0a1, crash in nsTArray_base<nsTArrayFallibleAllocator, nsTArray_CopyWithConstructors<JS::Heap<JSObject*> > >::IncrementLength(unsigned int) | mozilla::net::HttpBaseChannel::ApplyContentConversions() </li>

Comment 6: workaround browser.cache.use_new_backend_temp = false

Læs dette svar i sammenhæng 👍 5

Alle svar (6)

more options

You can try to (re)install the previous Aurora build to see if that still works and install the current build in an other directory.

Make sure to make new profile(s) when testing.

more options

i have this problem too, it's more look like a serious bug than his personal problem

more options

I trust that you are aware that Aurora is an Alpha-2 level pre-release version intended for testing and reporting issues that are discovered. It is updated daily, and occasionally a regression will creep into the code causing. Aurora (and Nightly) is intended for serious testers who can read crash reports and file bug reports to help Mozilla create the future versions of Firefox; it is not intended for the faint of heart user who expects it to work day after day.

more options

lainiwaku you say that as if Aurora channel is even close to being a Release or a stable development channel. This is the fun part in testing as sometimes you get new stuff while other times there may be a checkin(s) that well causes crashes or regressions and such.

The Aurora and Nightly is not updated daily however the checkins happens almost everyday so therefore it seems like it they have a update each day.

Also if you have other builds of Firefox like the 30.0 Release you should not share the same Profile between say Aurora channel builds and a Release.

more options

Valgt løsning

See also:

  • bug 1031697 - Aurora32.0a1, crash in nsTArray_base<nsTArrayFallibleAllocator, nsTArray_CopyWithConstructors<JS::Heap<JSObject*> > >::IncrementLength(unsigned int) | mozilla::net::HttpBaseChannel::ApplyContentConversions() </li>

Comment 6: workaround browser.cache.use_new_backend_temp = false

more options

cor-el Brilliant, thank you for the help. (:

the-edmeister Thankfully, I do not fit into your small box. Why use Aurora, you ask? I have my reasons, that is why. (: