Firefox 33.1.1 (newest) will not start with OS X 10.10.2.
I'm a OS X developer and yesterday upgraded to OS X 10.10.2 and now Firefox will not start. I get the menu bar and then the progress spinner just spins.
The force quit report is rather long, but I use Firefox as my default browser and miss it rather quickly.
Thank you! John
Here is a copy of the force quit report:
Date/Time: 2014-11-22 08:25:53 -0700 OS Version: 10.10.2 (Build 14C68k) Architecture: x86_64h Report Version: 21
Command: Firefox Path: /Applications/Firefox.app/Contents/MacOS/firefox Version: 33.1.1 (3314.11.13) Parent: launchd [1] PID: 1003
Event: hang Duration: 1.60s (process was unresponsive for 10 seconds before sampling) Steps: 17 (100ms sampling interval)
Hardware model: MacBookAir6,1 Active cpus: 4
Fan speed: 1198 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:
17 ??? (<FDCF73E5-44F9-31E4-8000-1E3A613AB670> + 1139319) [0x102116277] 17 __psynch_cvwait + 10 (libsystem_kernel.dylib + 90422) [0x7fff9462d136] *17 psynch_cvcontinue + 0 (pthread + 26908) [0xffffff7f80f4491c]
Process: firefox (Firefox) [1003]
Path: /Applications/Firefox.app/Contents/MacOS/firefox
Architecture: x86_64
Parent: launchd [1]
UID: 501
Task size: 41789 pages (+2)
CPU Time: 0.005s
Note: Unresponsive for 10 seconds before sampling
Note: 2 idle work queue threads omitted
opRun + 1371 (CoreFoundation + 466939) [0x7fff90efcffb] 1-17
17 __CFRunLoopServiceMachPort + 212 (CoreFoundation + 469812) [0x7fff90efdb34] 1-17
17 mach_msg_trap + 10 (libsystem_kernel.dylib + 70878) [0x7fff946284de] 1-17
*17 ipc_mqueue_receive_continue + 0 (kernel + 1173408) [0xffffff800031e7a0] 1-17
Thread 0x859 DispatchQueue 2 17 samples (1-17) priority 46
<thread QoS user interactive, IO policy important>
17 _dispatch_mgr_thread + 52 (libdispatch.dylib + 19050) [0x7fff932dca6a] 1-17
17 kevent64 + 10 (libsystem_kernel.dylib + 94770) [0x7fff9462e232] 1-17
*17 ??? (kernel + 5992224) [0xffffff80007b6f20] 1-17
Thread 0x8c8 17 samples (1-17) priority 46
<thread QoS user interactive, IO policy important>
17 thread_start + 13 (libsystem_pthread.dylib + 5149) [0x7fff93c8241d] 1-17
17 _pthread_start + 176 (libsystem_pthread.dylib + 12773) [0x7fff93c841e5] 1-17
17 _pthread_body + 131 (libsystem_pthread.dylib + 12904) [0x7fff93c84268] 1-17
17 _NSEventThread + 137 (AppKit + 1601435) [0x7fff89475f9b] 1-17
17 CFRunLoopRunSpecific + 296 (CoreFoundation + 464984) [0x7fff90efc858] 1-17
17 __CFRunLoopRun + 1371 (CoreFoundation + 466939) [0x7fff90efcffb] 1-17
17 __CFRunLoopServiceMachPort + 212 (CoreFoundation + 469812) [0x7fff90efdb34] 1-17
17 mach_msg_trap + 10 (libsystem_kernel.dylib + 70878) [0x7fff946284de] 1-17
*17 ipc_mqueue_receive_continue + 0 (kernel + 1173408) [0xffffff800031e7a0] 1-17
Сви одговори (1)
Well there are certainly a number of signatures that are being seen in the current versions of others top crashers in last 7 days for Mac OS like Corefoundation, libdispatch.dylib etc. But I would not know where to start from this angle andI have not seen any crash reports for 10.10.2 yet.
This is the boiler plate for troubleshooting start up issues with Firefox and can narrow down to make sure its not a plugin or something trivial: Firefox won't start - find solutions
Starting Firefox with the Profile Manager may also reveal any errors with the profile Profile Manager - Create, remove or switch Firefox profiles
Please post back with the results, however to set the right expectations, this is looking like a bug will need to be filled. Bugzilla.mozilla.org will be where that happens :-)