Firefox crashes
Hi.
Issue #1: FF (13.0.1) and all prior versions will not PASTE DATA (text AND other content) TO AOL desktop app 9.7 build 16.4343.30(or earlier) for Windows XP.(always reproducible). This causes the Firefox browser and/or the AOL app to become unresponsive. If Firefox is forced to close from the processes tab in task manager AOL will begin responding again.
Issue #2: FF (13.0.1) and all prior versions will not PASTE data (text and other content) TO MS Word 2003 (occurs SOMETIMES). If Firefox is forced to close from the processes tab in task manager MS Word will begin responding again.
Crash does NOT occur when data is copied FROM AOL or MS Word to the address bar of Firefox.
Crash does NOT occur when data is copied FROM Firefox TO Notepad or Chrome.
Crash does NOT occur when data is copied FROM Notepad or Chrome TO Firefox.
Makes no difference whether add-ons are disabled or enabled.
All add-ons are up-to-date.
Wybrane rozwiązanie
Hey; that did the trick!!! I disabled Silverlight in the add-ons, I believe (or extensions), and so far so good on importing/exporting text to/from firefox from different applications; so, yes, that fixed it :-D Should it reoccur, I will update here. Thank you again :-)
James
Przeczytaj tę odpowiedź w całym kontekście 👍 0Wszystkie odpowiedzi (12)
Skype Click to Call has been reported to cause such issues with the clipboard, but that doesn't show up in your system details list.
Maybe other software or Firefox extensions that use binary components can has a similar effect.
- https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
- https://support.mozilla.org/kb/Troubleshooting+plugins
See:
If you have submitted crash reports then please post the IDs of one or more crash reports (bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
- You can find the IDs of the submitted crash reports on the about:crashes page.
- You can open the about:crashes page via the location bar, like you open a website.
See:
Zmodyfikowany przez cor-el w dniu
Hello, Cor-el:
Thank you for your reply.
I have tried operating FF in the past (ALL versions) without extensions, and the same issue manifested itself.
I will check the links you provided (thank you) https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes https://support.mozilla.org/kb/Troubleshooting+plugins and see if I can find anything; I am using the default theme at this time (actually, I don't know if I've ever used a theme in FF).
Thus, I feel I have eliminated the extensions as a causal factor, unless, even in a "disabled" state, that the extensions could create an issue?
It is VERY annoying that the ONLY way I can copy information into FF is by first copying the info into "notepad" and then into FF (although, I can copy info from Chrome into FF....that is the only exception).
I did research the issue prior (the about:crashes reports) and, I did not see the "crash" listed there, I only was able to find unrelated crashes. I do not know if this is due to the fact that FF becomes unresponsive and I can only "kill" FF by going into task manager and ending the firefox.exe PROCESS. The vast majority of the time I can't right click and close the program from the taskbar, nor can I kill the program from task manager in the "applications" tab; only trying to kill FF from the processes tab is effectual at closing FF.
If I "kill" the firefox.exe process, would a crash report still be generated/should a crash report still be generated?
Additionally, I am aware that (according to FF) that the RealPlayer extension (to download videos etc) is known to cause stability issues in FF 14. Again, regardless, I have not experienced ANY issues with prior versions with the Real Player extension OR this version. Again, to eliminate this as a potential causal factor, as stated above, I did disable all extensions and was still able to reproduce the lockup.
In Tools>>>Options>>>Advanced>>>Network>>>Connection>>>Settings, I've tried both "Use System Proxy Settings" and "Auto-Detect Proxy Settings for this Network." That doesn't seem to have made a difference one way or the other.
I'm listing the crash reports below (all that I was able to extract and submit):
Crash reports:
f14c966d-173c-47bd-8d15-ad7d8f79ed40 7/10/2012 11:32 AM
ef8a75f2-034d-4da4-a993-a97f06b99613 7/10/2012 11:32 AM
d1d83df2-325d-4813-8369-58435714ded3 7/10/2012 11:28 AM
8583d786-25d9-4bbf-a19b-a7d3daaf94ae 7/10/2012 11:28 AM
bp-35d8ca5c-0ae2-4a29-b04d-ea30d2120626 6/26/2012 4:50 PM
ca22d83a-9690-40a3-ba16-5be3c93b4bbc 4/13/2012 5:58 PM
bp-ed98efc8-ef6a-4c3c-8773-6b7a82120409 4/9/2012 1:03 AM
bp-90583603-3054-4926-91b1-6ce2e2120215 2/15/2012 9:14 AM
bp-0c0626fe-91d3-4281-b783-d501a2120112 1/12/2012 8:30 PM
bp-468c4b67-6d05-453e-a55d-537be2120112 1/12/2012 8:30 PM
So, I have no idea what to try next....I can email you a .nfo file of my system if that would help?
Thank you again; I appreciate your assistance.....
James
Try to disable SPDY by setting the Boolean pref network.http.spdy.enabled to false on the about:config page.
Hi cor-ell: That did not work unfortunately. Thank you for the tip though; is there anything else that I might try adjusting in the about:config settings page? Even if I copy then paste the text in the firefox address bar to an external application, it will lock up the other application when attempting to paste into the external application. Firefox will lockup as well when pasting plain text FROM another application INTO the firefox/address bar (or say, a part of a form on a ff webpage).
Again, the only consistent exception to this is that I can copy from Firefox into notepad and from notepad into firefox.
I look forward to your reply; and thank you again :-)
James
Do you have any recent crash reports from the Firefox version that you currently use?
Sorry for neglecting to mention a reply to that question. I did go into about:crashes, and all of the reports listed were ones that I had submitted previously (listed below). My current settings under Tools>>>options>>>advanced>>>general>>>system defaults>>>submit crash reports and submit performance data are both enabled/checked.
I think that the reason why there aren't "more" crash reports is that when the lockups occur, I have to go into the task manager and "manually kill" either the firefox process and/or the process for the application that became unresponsive. Given that I am "killing" FF manually, I don't think it is able to generate a crash report, and if I am just "killing" the other app/process that text was pasted into, then I don't think I would have a FF crash either since it is the other application. In the future, I will attempt to extract an error message from the event log in windows or in the program's log of errors (it doesn't go back more than a few days at the moment).
Thanks again; I REALLY appreciate your help,
James
f14c966d-173c-47bd-8d15-ad7d8f79ed40 7/10/2012 11:32 AM
ef8a75f2-034d-4da4-a993-a97f06b99613 7/10/2012 11:32 AM
d1d83df2-325d-4813-8369-58435714ded3 7/10/2012 11:28 AM
8583d786-25d9-4bbf-a19b-a7d3daaf94ae 7/10/2012 11:28 AM
35d8ca5c-0ae2-4a29-b04d-ea30d2120626 6/26/2012 4:50 PM
ca22d83a-9690-40a3-ba16-5be3c93b4bbc 4/13/2012 5:58 PM
ed98efc8-ef6a-4c3c-8773-6b7a82120409 4/9/2012 1:03 AM
90583603-3054-4926-91b1-6ce2e2120215 2/15/2012 9:14 AM
0c0626fe-91d3-4281-b783-d501a2120112 1/12/2012 8:30 PM
468c4b67-6d05-453e-a55d-537be2120112 1/12/2012 8:30 PM
I also found a reference that if the crash reports DON'T have a prefix of "bp;" that they did NOT get submitted successfully. I just went into the about:crashes, and all of them now have a "bp" in front after I submitted the ones that hadn't been submitted successfully. Now that I submitted the ones that hadn't been submitted above (sorry) they now reflect a date submitted of today, 8/25.
Also, would you like any of the report data from: %APPDATA%\Mozilla\Firefox\Crash Reports\ ?
thanks again,
James
Report ID Date Submitted
bp-f878803e-b416-40cb-87ce-3896b2120825 8/25/2012 1:11 AM
bp-d6c9c4c1-dee5-4004-841a-818112120825 8/25/2012 1:11 AM
bp-ed2eead8-55a4-46f7-aba9-3b40d2120825 8/25/2012 1:10 AM
bp-c3bba7ba-2880-44d9-9551-c08fe2120825 8/25/2012 1:10 AM
bp-f732d679-546e-4dae-bccd-32d112120825 8/25/2012 1:10 AM
bp-35d8ca5c-0ae2-4a29-b04d-ea30d2120626 6/26/2012 4:50 PM
bp-ed98efc8-ef6a-4c3c-8773-6b7a82120409 4/9/2012 1:03 AM
bp-90583603-3054-4926-91b1-6ce2e2120215 2/15/2012 9:14AM
bp-0c0626fe-91d3-4281-b783-d501a2120112 1/12/20128:30PM
bp-468c4b67-6d05-453e-a55d-537be2120112 1/12/20128:30 PM
That are problems with plugins, possibly Silverlight (agcore.dll).
Zmodyfikowany przez cor-el w dniu
Wybrane rozwiązanie
Hey; that did the trick!!! I disabled Silverlight in the add-ons, I believe (or extensions), and so far so good on importing/exporting text to/from firefox from different applications; so, yes, that fixed it :-D Should it reoccur, I will update here. Thank you again :-)
James
You're welcome
Hi, Cor-el: It would appear that the solution was short-lived; even with silverlight disabled, an external application (multiple apps) when exporting text to AND from firefox TO another application (MS Word 2003; AOL desktop client, MS Excel 2003). A crash will NEVER occur/be reproducible with this copy/paste to/from notepad (seemingly; the only exception). Just for the heck of it; I enabled Silverlight, closed firefox, opened firefox, DISabled it again, closed firefox, opened firefox and still had the issue. I'm at a complete loss at this point; I have NO idea what could've changed.
Data from %APPDATA%\Mozilla\Firefox\Crash Reports\ since I can't ever seem to get the mozilla crash reporter to appear (attached file/I'm sure you know what it looks like; but in case anyone else reads this thread :-)
Attaching pic of the directory from above %APPDATA%
Also, just to verify; there was NOTHING in the following directory path: C:\Documents and Settings\Owner\Application Data\Mozilla\Firefox\Crash Reports\pending so, I realize this makes it difficult to troubleshoot; given the fact that there are a lack of crash reports....
Thanks for your help (as always);
James And, the mozilla crash reporter has NEVER appeared
I am going to submit crash reports again, if available.
Also, at the link: http://kb.mozillazine.org/Mozilla_Crash_Reporter I found the following reference: "The value SubmitCrashReport needs to be set in HKEY_LOCAL_MACHINE\Software\Mozilla\Firefox\Crash Reporter for all users and HKEY_CURRENT_USER\Software\Mozilla\Firefox\Crash Reporter for a single user. When the DWORD value of SubmitCrashReport is 0, the Crash Report will not be submitted."
I did a "regedit" and verified in the key: HKEY_CURRENT_USER\Software\Mozilla\Firefox\Crash Reporter that the values are ALL set to "1" (enabled) and NOT "0" (disabled). For the following entries: EmailMe, IncludeURL, and SubmitCrashReport. There is an entry at the top however, Name: (default); Type: REG_SZ; Data: (value not set). Should there be data in this seemingly useless entry? Below that data is a field (named): Email, REG_SZ, [my email address]. As far as I can tell; the registry for the crash reporting functionality is working? Would that also be your assessment?
Would the crash reporter/breakpad still trigger even if I manually killed the firefox.exe process in the task manager?
Also, in the example of a crash report; Append the GUID portion of the Crash ID to the Breakpad report URL (currently http://crash-stats.mozilla.com/report/index/) and go to that URL to view the crash report (e.g., http://crash-stats.mozilla.com/report/index/031b02bb-26b6-4168-ac0e-2de492090531
I am guessing that when you append the /index/......... that you can leave out the "bp" (indicating a successful crash report submission)?
I am also going to attempt to get a stacktrace (see: https://developer.mozilla.org/en-US/docs/How_to_get_a_stacktrace_with_WinDbg) by downloading http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx and following the instructions since it states on the first page referenced here:
"Sometimes you need to get a stacktrace (call stack) for a crash or hang but Talkback or Breakpad fail because it's a special crasher or a hang. This article describes how to get a stacktrace in those cases with WinDbg on Windows."
It seems to be a rather involved process; downloading the 175 MB debugging program and the mozilla symbol packages...so, I'll see if I can come up with some data here that will help you; well help you help me identify any additional causal factors.
Thanks again for your help :-)
James