Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

Since version 36 upgrades, crash reporter comes up each time when asked to restart after getting newer updates while in version 36.

  • 4 wotmołwy
  • 6 ma tutón problem
  • 9 napohladow
  • Poslednja wotmołwa wot the-edmeister

fredfletcher
fredfletcher
more options

These problems started when upgraded to version 36. Each time there were newer upgrades while still in version 36, for example; when I check for a newer version in Help/About/check for updates, there have been 4 sub-upgrades 36.0.1, 36.0.2, 36.0.3, 36.0.4.

When I was asked to restart after it downloaded the upgrades, it closes my browser and then about 30 seconds later, the crash reporter comes up. This never happened before and is getting to be a concern at this point.

These problems started when upgraded to version 36. Each time there were newer upgrades while still in version 36, for example; when I check for a newer version in Help/About/check for updates, there have been 4 sub-upgrades 36.0.1, 36.0.2, 36.0.3, 36.0.4. When I was asked to restart after it downloaded the upgrades, it closes my browser and then about 30 seconds later, the crash reporter comes up. This never happened before and is getting to be a concern at this point.

Wšě wotmołwy (4)

FredMcD
FredMcD
more options

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP in front of the numbers, click it and select Submit.

Using your mouse, mark the most resent 7 - 10 crash reports, and copy them. Now go to the reply box below and paste them in.

Download Firefox Full Installer For All languages And Systems {web link}

fredfletcher
fredfletcher Prašer
more options

I wasn't entirely sure what you meant by copying the last 7-10, but here goes:

Report ID Date Submitted bp-b47e1d98-e6ea-4bad-9b5b-de60e2150321 21/03/2015 4:00 PM bp-a84a4926-e6f8-4b9c-8ea9-c8ae02150321 21/03/2015 11:27 AM bp-0230613b-864b-4b51-b7b7-352282150321 20/03/2015 8:18 PM bp-204f1055-3f4c-4e48-bd74-2e02e2150305 05/03/2015 3:47 PM bp-e04de17d-aa06-4a71-b11b-64f1a2150303 03/03/2015 3:25 PM bp-0454584c-cbe8-4119-84de-3615d2150210 09/02/2015 8:51 PM bp-2fcb6605-5ffd-44b7-bb54-09a372141218 18/12/2014 3:31 PM bp-c8eb0be7-deff-4e10-9bb1-3340b2141021 21/10/2014 4:24 AM bp-1533d68f-cc41-4c95-8c84-0f69e2141015 15/10/2014 12:56 PM bp-22b9f3af-06ad-43f9-8133-15c3c2140904 04/09/2014 8:36 AM

FredMcD
FredMcD
more options

Well done. Now let's see.

Some crash reports flagged this programs;

Signature shutdownhang

This is a new type of crash. The powers that be are working on it.

Another crash report says;

Signature shutdownhang

l3codecx.ax = MPEG Layer-3 Audio Codec for Microsoft DirectShow

the-edmeister
the-edmeister
  • Moderator
more options

I have been seeing the same problem on my WinXP installation where a Firefox 36+ update crashes upon the restart; just happened now when I did the Firefox 36.0.4 update. That happened a few times when 36 was in Beta, too - but not every time, but like 3 out of 10 updates when in Beta testing.

Also, the CPU load is much higher when the update is installing itself than I am accustomed to seeing - and when it crashes the CPU is pegged until I hit the "Restart and Report the crash" button in the Crash Reporter window. Restarts fine with the usual ~40% CPU load.

BTW, not happening with the next Beta - Firefox 38 which is the Developer / Aurora version right now.