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ć.

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

Since I updated to OSX 10.10.3 my firefox 37.0.2 is not working. What happened?

  • 6 wotmołwy
  • 1 ma tutón problem
  • 7 napohladow
  • Poslednja wotmołwa wot FredMcD

more options

Firefox was the default browser and I have been using it without any problems. Since the last update of Yosemite it is slow, does not respond quickly to google docs and crashes. I already re-installed it e times.

Firefox was the default browser and I have been using it without any problems. Since the last update of Yosemite it is slow, does not respond quickly to google docs and crashes. I already re-installed it e times.

Wšě wotmołwy (6)

more options

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac Options)
key, and then starting Firefox. Is the problem still there?


Start your Computer in safe mode with networking. Then start Firefox. Try Safe web sites. Is the problem still there?

Starting The Computer In Safe Mode;
Free Online Encyclopedia

more options

The problem persisted and I have a "couple" of lines in as a crash report:

Date/Time: 2015-04-21 17:36:37 -0300 OS Version: 10.10.3 (Build 14D136) Architecture: x86_64h Report Version: 21

Command: Firefox Path: /Applications/Firefox.app/Contents/MacOS/firefox Version: 37.0.2 (3715.4.15) Parent: launchd [1] PID: 358

Event: hang Duration: 1.00s (process was unresponsive for 71 seconds before sampling) Steps: 11 (100ms sampling interval)

Hardware model: MacBookAir6,1 Active cpus: 4

Fan speed: 2771 rpm


Timeline format: stacks are sorted chronologically Use -i and -heavy to re-report with count sorting


Heaviest stack for the main thread of the target process:

 11  ??? (<561CCB4F-4136-32BA-BBB9-C8FFF6593FED> + 30505261) [0x103d1792d]
 11  ??? (<2D84C6F3-0F0D-3E19-ACCB-E37D652BB369> + 264937) [0x100540ae9]
 11  ??? (<2D84C6F3-0F0D-3E19-ACCB-E37D652BB369> + 264357) [0x1005408a5]
 11  ??? (<2D84C6F3-0F0D-3E19-ACCB-E37D652BB369> + 263752) [0x100540648]
 11  ??? (<2D84C6F3-0F0D-3E19-ACCB-E37D652BB369> + 261944) [0x10053ff38]
 11  ??? (<2D84C6F3-0F0D-3E19-ACCB-E37D652BB369> + 358175) [0x10055771f]
 11  ??? (<2D84C6F3-0F0D-3E19-ACCB-E37D652BB369> + 2102857) [0x100701649]
 11  __psynch_mutexwait + 10 (libsystem_kernel.dylib + 90470) [0x7fff9a2fa166]
*11  psynch_mtxcontinue + 0 (pthread + 21926) [0xffffff7f80f655a6]


Process: firefox (Firefox) [358] Path: /Applications/Firefox.app/Contents/MacOS/firefox Architecture: x86_64 Parent: launchd [1] UID: 501 Task size: 62386 pages CPU Time: 0.004s Note: Unresponsive for 71 seconds before sampling Note: 2 idle work queue threads omitted.... .......

more options

We need to see the whole report, it covers several pages.

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.

more options

Ok, here are the rashes reports: bp-351b5dbb-4a0d-4f1b-8420-3b6682150421 21/04/15 18:42 bp-939736fa-84a4-4b50-946f-6a4062150421 21/04/15 18:42 bp-16fe4216-6a53-4e97-89a7-2365a2150421 21/04/15 18:40 bp-449015a5-3b0f-422c-9ef9-954222150421 21/04/15 18:40 bp-56012b61-4055-4d7b-b76a-bce132150421 21/04/15 18:40 bp-eb69b4b3-121f-4586-9c0f-ae3622150421 21/04/15 10:23 bp-517d9142-6430-4747-92b9-9f1642150415 15/04/15 15:46 bp-4b1609c7-6d63-4815-9120-80cec2150410 10/04/15 14:46 bp-f215d3a3-2887-4296-93bf-2602e2150410 10/04/15 10:49 bp-7ae6450b-235b-455e-91aa-1a0572150409 09/04/15 15:16

Thanks

more options

The recent crash reports have an @ EMPTY signature and are from Firefox 36.

Did Firefox crash after updating to 37.0.2?

Try to disable IPv6 (check for other possible causes as well).

Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem.

  • Switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance
  • Do NOT click the Reset button on the Safe Mode start window
more options

Process Type plugin Java Applet Plug-in Version:Java 7 Update 75

JavaRuntimeSupport

libjvm.dylib = NetBeans on Mac

libjava.dylib = Java ?

QuartzCore = Core Animation

Foundation


Check for updates for all of the above