Firefox crashes
Firefox crashes at launch, in both normal and safe modes
すべての返信 (5)
In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.
The crash report is several pages of data. We need the report numbers to see the whole report.
Using your mouse, mark the most recent 7 - 10 crash reports, and copy them. Press the Reply button. Now go to the reply box and paste them in.
For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support
011427C5-5AF8-4F31-A03C-20048BAA5406 6/21/17 8:34 AM 0B43E028-0F3D-4843-8DAF-707585A626C7 6/21/17 8:31 AM D36FF360-4B75-4C0D-BCBB-DCF48865C729 6/21/17 8:31 AM 5E5CD5F4-365D-459B-B385-2D088FB54A5F 6/21/17 8:19 AM 5AA12664-A03E-42B8-A5DD-E68C52F13E6A 6/21/17 8:19 AM E554CBF4-DC19-4EC1-8808-5CEDB51A910F 6/20/17 9:59 PM 594C30EB-BE41-4A0F-949E-DCC6414212E3 6/20/17 9:55 PM 9BD24A3A-C4EF-4C87-AE8C-78437ADA6645 6/20/17 6:58 PM D6B2A6CC-ACD2-46F6-B05E-B73F0A427602 6/20/17 6:58 PM 52F15E4E-97ED-4E3C-8C38-C7BB210011DB 6/20/17 6:58 PM 9528F1A1-54D6-4448-A7EC-E20D3F1BE802 6/20/17 6:58 PM 998DB129-3085-4F89-A6B0-ED819CCB46AF 6/20/17 6:58 PM 1B5ECF0B-A143-4584-B69B-E8AD0927F38E 6/20/17 6:58 PM 62DA3D2C-1D4C-4CD4-B344-CB2B7680B838 6/20/17 6:58 PM 9E611285-0843-49D9-9ECD-1EEE0887286D 6/20/17 6:58 PM 20686454-C0B9-47D0-8464-7676D65AE68C 6/20/17 6:57 PM
Some of your crash reports weren’t sent to the Mozilla Servers.
In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.
The crash report is several pages of data. We need the report numbers to see the whole report.
bp-0f1b39e6-d9e3-4ed7-ad63-9d3eb0170621 6/21/17 2:53 PM bp-17688b8d-f550-4ba9-a6c5-a40ee0170621 6/21/17 2:53 PM bp-b15d88c8-2cd0-4587-8b3d-0e2630170620 6/19/17 10:32 PM bp-ea9888fb-80cb-4176-992b-ab2221170620 6/19/17 10:29 PM bp-21276190-c747-4996-9c74-2ad4b1170620 6/19/17 10:29 PM bp-fef36e8c-f5ec-4dce-9221-ee3eb1170619 6/19/17 1:10 PM bp-5b61dc23-de5b-4b17-9144-9a2761170619 6/19/17 12:32 PM bp-7eca6138-383d-4a17-a755-ab0351170619 6/19/17 12:32 PM bp-2426c6ea-c31e-4133-8c7d-304a72161222 12/22/16 2:18 PM bp-1b4e230c-716c-45e5-a064-7757f2161220 12/19/16 4:00 PM bp-ddfc8033-65c8-4346-8a97-3f00f2161220 12/19/16 4:00 PM bp-73fe817d-3730-4c2f-9120-92bbe2161214 12/14/16 12:23 PM bp-137de2dc-52c4-4b01-98a9-c514d2160808 8/8/16 11:14 AM bp-1d28d6d2-9b34-4372-90ee-4d5042160710 7/10/16 4:26 PM bp-7c38c868-504a-41dc-a6c8-df2142160628 6/28/16 4:53 PM bp-062ecdf2-90c1-48fe-bb41-28a972160409 4/9/16 10:25 AM bp-9352e8be-b13b-495d-a1a3-1dc012160317 3/16/16 9:17 PM
Thank you for the report IDs. I only checked the first 8, all caused by an incompatibility with "MySpeed". There is a MySpeed update to address this that was released in March:
http://www.enounce.com/support-known-issues/ki235
That might not be the latest version now, so you might also try to trigger an update from within the product.