Twitter - and seemingly ONLY Twitter - routinely causes Firefox to crash.
- Shockwave Flash 32.0 r0
- User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:67.0) Gecko/20100101 Firefox/67.0
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 Submitted crash reports, and copy them. 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
I believe this is what you're asking for. If not, let me know and I'll grab whatever you need, thanks.
bp-54728d16-fb16-4b20-b8b5-afb080190323 bp-c74b6dca-5976-4466-8c41-a0ba30190305 bp-4237e562-a374-4643-8afa-4acf20190304 bp-3932422d-9496-4622-9340-bba0a0190118 bp-9257aeba-0a42-471a-8034-b7e500181119 bp-26bb371d-8b51-4442-ba02-33c5d0181119 bp-e03ee311-de0e-4fe7-9b0f-a81cb0181119
That was very good work. Well done.
Product Firefox Release Channel beta Version 67.0b4 Build ID 20190322012752 (2019-03-22) Buildhub data OS OS X 10.14 OS Version 10.14.3 18D109
Sat, 23 Mar 2019 22:27:41 GMT bp-54728d16-fb16-4b20-b8b5-afb080190323 Signature: free | mozilla::net::nsHttpConnectionMgr:: ProcessNewTransaction
Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS ++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel beta Version 66.0b12 Build ID 20190228180200 (2019-02-28)
Mon, 04 Mar 2019 02:02:55 GMT bp-c74b6dca-5976-4466-8c41-a0ba30190305 Signature: mozilla::net::nsSocketTransportService:: OnDispatchedEvent
Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS +++++++++++++++++++++++++++++++++++++++++++ Mon, 04 Mar 2019 17:50:18 GMT bp-4237e562-a374-4643-8afa-4acf20190304 Signature: poll
Crash Reason EXC_BAD_ACCESS / EXC_I386_GPFLT
This is for Sumo's Related Bugs 1528756 RESOLVED DUPLICATE Crash on @ poll
1516325 You are not authorized to access bug 1516325. +++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel beta Version 65.0b11 Build ID 20190114172331 (2019-01-14)
Fri, 18 Jan 2019 19:38:07 GMT bp-3932422d-9496-4622-9340-bba0a0190118 Signature: mozilla::ipc::WriteIPDLParam<T>
Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS
This is for Sumo's Related Bugs 1490677 You are not authorized to access bug
1484524 RESOLVED FIXED Crash in static void mozilla::ipc::IPDLParamTraits<T>::Write
Ændret af FredMcD den
Most of the reports are too old to be useful. I see you have been using the beta version. Betas are prone to problems.
Try removing the current browser. Then get the full installer for beta.
Beta, Developer, Nightly versions https://www.mozilla.org/en-US/firefox/channel/desktop/
Here's one from a few minutes ago, again, caused by Twitter.
If I need to, I'll switch over to the release version. I kind of like running the beta specifically so that I can report issues if need be. And I do have a separate Twitter client that I can resort to. Just seems odd that Twitter reliably crashes FF after browsing it for a short while.
If it helps at all, there are some indications that it's about to cause a crash. Clicking on images (on Twitter) brings up the frame/div that the image is supposed to occupy, but the image itself doesn't load. The crash above was presaged by clicking on a video on a Twitter post that did the same thing - everything about the post came up except the video (it was a YouTube linked video).
Another interesting side note - after such a crash, if I click "Restart Firefox" in the crash window, Firefox does actually come back up, but it's unable to connect to any web sites. I have to close it, then reopen it. Then it works fine.
Product Firefox Release Channel beta Version 67.0b4 Build ID 20190322012752 (2019-03-22)
bp-eb6a0909-ea3f-41f1-9708-6533d0190324 Signature: poll
Crash Reason EXC_BAD_ACCESS / EXC_I386_GPFLT
1528756 RESOLVED DUPLICATE Crash on @ poll
1516325 You are not authorized to access bug
I called for more help.
. . . . caused by Twitter.
Does this happen on other sites?
Installing the normal version would be a good idea if only to see if the problem remains.
Nope. Exclusively Twitter.
Try to disable IPv6 (check for other possible causes as well).
You can check the connection settings.
- Options/Preferences -> General -> Network: Connection -> Settings
If you do not need to use a proxy to connect to internet then try to select "No Proxy" if "Use the system proxy settings" or one of the others do not work properly.
See "Firefox connection settings":