Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.
v23 crashes constantly since Update Tuesday
Since Update Tuesday from Microsoft (13 Aug 2013), v23.0 has been crashing unpredictably and almost constantly. This might, in theory, be related to the most recent update to Ghostery, but there was a crash prior to the Ghostery update that installed later on 13 August.
- Occurs with both single session and multiple tabs
- Occurs with flash running and flash not running/visible on on tab
- Occurs when browsing the 'net and when viewing (previously OK) files on disk, even when the 'net is explicitly turned off
Session restore DOES appear to work.
System basics: Win7Pro32, HP Pro Book, although I've experienced this on multiple machines with a variety of Win7 setups
Related crashes: Thunderbird is also misbehaving a bit since Update Tuesday, although not nearly so severely... and only (about 1 in 4) when Firefox has also just crashed.
NB2 I will NOT use the "automated crash reporter" because much of my work involves privileged information and investigations in progress.
All Replies (20)
Can you please submit a Crash Report so we can figure out what is goign on here? It doesn't include any personally identifiable information (here's one of mine if you want to see, https://crash-stats.mozilla.com/repor.../3ab3ade3-643f-484c-b7c7-f92052130618) but will let us actually see what's crashing instead of guessing.
fixed broken link ~J99
Okulungisiwe ngu NoahSUMO
No can do -- (1) The crash reports DO identify the sites, and I can't have that released during an investigation; and... (2) The crash reports aren't even being generated. For example, v23 crashed twice while I was attempting to respond to this request, and neither generated a crash report on disk when I said "do not send automatically"
1: No, crash reports don't include the page you are on. Not sure where you get that from. 2. As for this, ok, that's another issue. Try disable Hardware Acceleration, Turning off hardware acceleration
We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash ID's to help us learn more about your crash.
- Enter about:crashes in the address bar (that's where you enter your website URL) and press Enter. You should now see a list of submitted crash reports.
- Copy the 5 most recent crash ID's that you see in the crash report window and paste them into your response here.
Thank you for your help!
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) as a test to see if that helps.
Create a new profile as a test to check if your current profile is causing the problems.
See "Creating a profile":
If the new profile works then you can transfer some files from an existing profile to the new profile, but be careful not to copy corrupted files.
Replying to a bunch of stuff at once:
(1) Turning off hardware acceleration has no effect (2) "Freshening" the profile has no effect -- it took less than five minutes to crash while idling in the background (3) There aren't any crashes from this that are generating crash profiles, and as noted above I'm not submitting crash reports anyway, so wacka-flocka-flame's request is going to go... unanswered. (Not to mention that at least for some prior versions of Firefox, it IS possible to recover URLs from crash reports -- I've done it.) (4) Next, I will try a force-reinstall of all of the Update Tuesday updates, in case that is the problem... but that's going to run more than an hour and a couple of reboots
We cant fix your crash if youre not submitting them.
Note that you can inspect what is getting send and edit this text to remove all privacy sensitive parts of it.
I'm having the same problem with Firefox 23.0. I do have crash reports and would love assistance restoring (or at least finding a list of) my many lost windows and tabs. Thank you very much!
Can everyone wait for the firefox 23.0.1 release in a couple of days?
Again, several items updating at once...
- reinstalling flash didn't help (but with adobe's crappy interfaces and disrespect for privacy, that's not much of a surprise); processexplorer shows two flash processes running
- resetting all of the windows updates, then reinstalling one by one, didn't help
- processexplorer reports that Firefox is now taking up about 270mb more under v23.0 than it did under v22.0
... and I'll wait for 23.0.1, but it would be nice if anticipated maintenance-release dates were posted somewhere visible...
Since you're so insistent: https://crash-stats.mozilla.com/report/index/bp-b7d35575-f686-4161-bcf5-afb232130816
(A carefully sanitized session. I still find this an unwarranted and unnecessary system.)
Inference: There's a memory-leak problem again, caused by some code change between v22.0 and v23.0. It may, or may not, be related to the flash sandbox; there was no flash on any of the pages in that crash. It may, or may not, be related to refusal to accept certain advertising cookies, although the off-net behavior seems to deny that.
This crash is caused by ghostery, try disabling or removing it.
Highly doubtful, since (as noted in the initial report) the crashes began BEFORE Ghostery updated. I'll give it a try nonetheless.
"Can't everyone wait a few days for 23.0.1?"
No. I can't remember how long it's been since FF has crashed on me, yet after updating to 23.0.1 today it's crashed twice. Twice in one day. And no, I don't use Ghostery.
@Tylerdowner "1: No, crash reports don't include the page you are on. Not sure where you get that from."
The crash report *says* it will report what page you're on. I'm sure FF will crash again soon, I'll take a screenshot for you. On second thought, screenshot unnecessary.
"Include the address of the page I was on."
Okulungisiwe ngu HelloWorld
The crash report has a checkbox, if you want to report the page, or not, so your assumption is incorrect.
Okulungisiwe ngu kobe
Yes, it HAS a checkbox.
@Tylerdowner's claim was ""1: No, crash reports don't include the page you are on. Not sure where you get that from", which is grossly INACCURATE....as are you.
Defending inaccurate information is hardly helpful to the community at large. Tylerdowner was wrong. Get over it already.
I know we're getting off topic here, but if you include URLs in your reports and you view the report online using a link from the about:crashes page, do you see the URL there? It's possible that some crash data is not on the public page.
Hi Biscuit1001, if you view your crash data online using a link on the about:crashes page, and scroll down on the first tab, there often is a section with one or more links to Bugzilla showing the status of research or fixes for a particular crash signature. You might take a look at that.
You've *got* to be kidding me, right? This is the kind of "help" being offered here to resolve Firefox problems/bugs (no, "features"?)?
"1: No, crash reports don't include the page you are on." by Tylerdowner was an obvious (albeit, lame) attempt at denial. The st00pid is so strong with this one that it reeks of cheap cologne.
Which begs the question, are you, or were you ever gainfully employed by AOL? If so, please, do everyone else a favor and, to put it frankly, 'Don't quit your day job'.
As you can clearly see in the provided screen cap, oh guru of whizz-dumb, there is, in fact, a checkbox which clearly states the following: "Include the address of the page I was on" which would be added to the crash report.
If it weren't for the fact that you, mister moderator, didn't pay enough attention , you would have noticed. I'd apologize in advance for smacking you upside the head with a cl00-by-four, but I see no reason in doing so. Do kindly unpuff your chest. It's unbecoming and quite honestly, ghastly.
I should also mention that I use Ghostery (version 5.0.3) with Firefox 23.0.1 (not the buggy stub installer, mind you) and have yet to experience the issues discussed within this thread.
Abusive language removed by moderator
Okulungisiwe ngu NoahSUMO