Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

We're Sorry. Firefox had a problem and crashed.

811 views
Skip to first unread message

Tonya Marshall

unread,
Dec 20, 2015, 2:36:07 PM12/20/15
to mozilla-sup...@lists.mozilla.org
This happens with pretty good regularity - about once a day. I did save
the details of the crash in a text document if anyone wants to see them.


We're Sorry.
Firefox had a problem and crashed.
We'll try to restore your tabs and windows when it restarts.

I have the following choices checked:
-Tell Mozilla about this crash so they can fix it
-Include the address of the page I was on
-Allow Mozilla to contact me about this report.

My OS: Linux, vFedora 22
Firefox: v42.0

VanguardLH

unread,
Dec 20, 2015, 6:24:36 PM12/20/15
to mozilla-sup...@lists.mozilla.org
I found that dialog to be useless. Maybe it helps Mozilla but it
doesn't help me. Just more nuisance. I'm using Windows 7, not Linux,
but the popup still doesn't help me. I figure there are plenty of users
with the install-time defaults that can report problems with Mozilla.
I'm not going to be one of them.

"Option -> Advanced -> Data Choices -> Enable Crash Reporter" was
already disabled but I was still getting the popup about Firefox
crashing (usually long after I already exited it).

For old versions, you edited application.ini:

[Crash Reporter]
Enabled=1

and changed Enabled to 0 (zero).

I was still getting the popup about crashes although I set "Options ->
Advanced -> Data Choices -> Enable Crash Reporter" to disabled. I went
to about:crashes and cleared those out. Since then, no more popups
about crashes (and nothing listed in about:crashes) but then I don't
know if there have been crashes (when I'm not even using Firefox because
I told it to exit long ago).

I suppose I could also rename crashreporter.exe to something else, like
changing the extension to .DISABLE_exe but I'll wait until I see another
unwanted and useless-to-me popup about a crash.

On trying to load Firefox, I've also gotten a popup saying Firefox was
still running but I had exited it long ago. I suspect one of the
add-ons is not unloading which keeps Firefox loaded. Mozilla needs to
first do a graceful request to get add-ons to unload but if they don't
after a timeout period then forcibly terminate them. If the user exits
Firefox, it should really exit.

Those popups only show up maybe twice per week for me. If they are
happening several times every day for you then I would disable all the
add-ons you installed and retest Firefox's stability.

While I didn't find useful info in the crash files, they are text files
so you can open them with any text editor. Or go to about:crashes and
click on the links there to look inside. Maybe in your scenario they
may reveal why Firefox is crashing so much for you.

WaltS48

unread,
Dec 20, 2015, 6:57:38 PM12/20/15
to mozilla-sup...@lists.mozilla.org
On 12/20/2015 02:35 PM, Tonya Marshall wrote:
> This happens with pretty good regularity - about once a day. I did save
> the details of the crash in a text document if anyone wants to see them.
>
>


You could enter about:crashes in the address bar, right click on the
most recent Submitted Crash report, select Copy Link Location, and paste
it in a followup post. It would probably be more informative than your
text document.

Mine would be
https://crash-stats.mozilla.com/report/index/bp-049007a5-3f1e-4c9c-a48a-ca8622151217

I usually include the address of the page I was on, but don't allow them
to contact me.

--
Linux Mint 17.2 "Rafaela" | KDE 4.14.2 | Thunderbird 45.0a2 (Earlybird)
You don't need zero-days when machines wherever are packed with old-days.
Go Bucs! (next season) Go Pens! Go Sabres! Go Pitt!
[Visit Pittsburgh]<http://www.visitpittsburgh.com/>
[Coexist · Understanding Across Divides]<https://www.coexist.org/>

Tonya Marshall

unread,
Dec 20, 2015, 8:57:34 PM12/20/15
to mozilla-sup...@lists.mozilla.org
On 12/20/2015 03:57 PM, WaltS48 wrote:
> On 12/20/2015 02:35 PM, Tonya Marshall wrote:
>> This happens with pretty good regularity - about once a day. I did save
>> the details of the crash in a text document if anyone wants to see them.
>>
>>
>
>
> You could enter about:crashes in the address bar, right click on the
> most recent Submitted Crash report, select Copy Link Location, and paste
> it in a followup post. It would probably be more informative than your
> text document.
>
> Mine would be
> https://crash-stats.mozilla.com/report/index/bp-049007a5-3f1e-4c9c-a48a-ca8622151217
>
>
> I usually include the address of the page I was on, but don't allow them
> to contact me.
>

Hey, Walt, that's pretty cool. Thanks! Here's my latest crash report.

https://crash-stats.mozilla.com/report/index/c114dc7f-bbf9-425b-9444-6288d2151220

VanguardLH

unread,
Dec 20, 2015, 9:45:11 PM12/20/15
to mozilla-sup...@lists.mozilla.org
Tonya Marshall wrote:

> https://crash-stats.mozilla.com/report/index/c114dc7f-bbf9-425b-9444-6288d2151220

Turn off hardware acceleration (uses the video card's GPU). Doesn't
seem web browsers have this down right yet and video card makers aren't
designing their drivers for this type of use.

Options -> Advanced -> General -> Use hardware acceleration

»Q«

unread,
Dec 20, 2015, 9:49:55 PM12/20/15
to mozilla-sup...@lists.mozilla.org
In
<news:mailman.434.1450663051...@lists.mozilla.org>,
Tonya Marshall <nos...@xyz.net> wrote:

> https://crash-stats.mozilla.com/report/index/c114dc7f-bbf9-425b-9444-6288d2151220

Updating to Fx 43 may help. I understand nothing of the details, but
43 is supposed to have lots of fixes for GTK+3 support, and the
"crashing thread" section at the end of your report indicates that's
where your trouble is coming from. Also, it looks like all the reports
with that crash signature are for Fx 41 and 42.



Tonya Marshall

unread,
Dec 20, 2015, 9:54:07 PM12/20/15
to mozilla-sup...@lists.mozilla.org
Thanks. I'll have to wait until Fedora gets the new 43 update. Hopefully
it won't be long.

VanguardLH

unread,
Dec 20, 2015, 11:08:40 PM12/20/15
to mozilla-sup...@lists.mozilla.org
Tonya Marshall wrote:

> I'll have to wait until Fedora gets the new 43 update. Hopefully it
> won't be long.

Why do you have to wait to get a new version of the operating system to
get a new version of an application? Just download Firefox and install.

Tonya Marshall

unread,
Dec 21, 2015, 12:21:15 AM12/21/15
to mozilla-sup...@lists.mozilla.org
I meant that I need to wait until Fedora gets the new 43 update of
Firefox in the repos; sorry for the confusion.

WaltS48

unread,
Dec 21, 2015, 8:53:03 AM12/21/15
to mozilla-sup...@lists.mozilla.org
I noticed on the Fedora forum that they build Firefox with GTK+3
support. Mozilla disabled it in 43 and 44, so what Fedora does could be
the cause of your crashes.

I would make sure your system is up to date with all patches, see if
that helps, and wait for Firefox 43 from the repo.

Fedora 23 is available. <https://getfedora.org/en/workstation/download/>

»Q«

unread,
Dec 21, 2015, 11:39:20 AM12/21/15
to mozilla-sup...@lists.mozilla.org
In
<news:mailman.472.1450705980...@lists.mozilla.org>,
WaltS48 <thali...@REMOVEaim.com> wrote:

> On 12/21/2015 12:20 AM, Tonya Marshall wrote:

> > I meant that I need to wait until Fedora gets the new 43 update of
> > Firefox in the repos; sorry for the confusion.
>
> I noticed on the Fedora forum that they build Firefox with GTK+3
> support. Mozilla disabled it in 43 and 44, so what Fedora does could
> be the cause of your crashes.
>
> I would make sure your system is up to date with all patches, see if
> that helps, and wait for Firefox 43 from the repo.

Thanks -- I didn't know it had been pushed back. Red Hat seems to
really want this AFAICT, which explains why Fedora is shipping it
already.

It looks like it was pushed back so that Fx 44 will be able to tell
people who try to update to 45 but who have only GTK+2 that their
systems are no longer supported.
<https://bugzilla.mozilla.org/show_bug.cgi?id=1227023>




0 new messages