When I try to make a new post in Facebook on Firefox 53, it frequently crashes
When I try to make a new post in Facebook on Firefox 53, it frequently crashes - as soon as I place the cursor in the blank for a new post, the area in which to make a new post disappears. I end up using Google Chrome (which I dislike) to make a new post.
For about 1.5 to 2 months, this has been happening. I even did a reinstall of Windows 10 on my Asus notebook (not for this reason) and then installed Firefox fresh - that was about 1 month ago. The problem occurred right away after they were both reinstalled.
I have Windows 10 Home Edition Version 1703 64-bit operating system, x-64-based processor
I see Firefox version is listed as 53.0.3 (32-bit)
I wonder if Firefox version is supposed to be "64-bit"? I notice that even though I have a 64-bit computer, frequently the software installed is the "32-bit" version.
Additional System Details
Installed Plug-ins
- Shockwave Flash 25.0 r0
Application
- Firefox 53.0.3
- User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0
- Support URL: https://support.mozilla.org/1/firefox/53.0.3/WINNT/en-US/
Extensions
- Application Update Service Helper 2.0 (aushelper@mozilla.org)
- Download Sound 1.2 (jid1-1vdAiX6gThdiIg@jetpack)
- Gmail™ Notifier (restartless) 0.7.4 (jid0-GjwrPchS3Ugt7xydvqVK4DQk8Ls@jetpack)
- Multi-process staged rollout 1.14 (e10srollout@mozilla.org)
- Pocket 1.0.5 (firefox@getpocket.com)
- Shield Recipe Client 1.0.0 (shield-recipe-client@mozilla.org)
- uBlock Origin 1.12.4 (uBlock0@raymondhill.net)
- Web Compat 1.0 (webcompat@mozilla.org)
Javascript
- incrementalGCEnabled: True
Graphics
- adapterDescription: Intel(R) HD Graphics 5500
- adapterDescription2:
- adapterDeviceID: 0x1616
- adapterDeviceID2:
- adapterDrivers: igdumdim64 igd10iumd64 igd10iumd64 igd12umd64 igdumdim32 igd10iumd32 igd10iumd32 igd12umd32
- adapterDrivers2:
- adapterRAM: Unknown
- adapterRAM2:
- adapterSubsysID: 19ad1043
- adapterSubsysID2:
- adapterVendorID: 0x8086
- adapterVendorID2:
- crashGuards: []
- currentAudioBackend: wasapi
- direct2DEnabled: True
- directWriteEnabled: True
- directWriteVersion: 10.0.15063.0
- driverDate: 11-10-2016
- driverDate2:
- driverVersion: 20.19.15.4549
- driverVersion2:
- featureLog: {u'fallbacks': [], u'features': [{u'status': u'available', u'description': u'Compositing', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'HW_COMPOSITING'}, {u'status': u'available', u'description': u'Direct3D11 Compositing', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'D3D11_COMPOSITING'}, {u'status': u'disabled', u'description': u'Direct3D9 Compositing', u'log': [{u'status': u'disabled', u'message': u'Disabled by default', u'type': u'default'}], u'name': u'D3D9_COMPOSITING'}, {u'status': u'available', u'description': u'Direct2D', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'DIRECT2D'}, {u'status': u'available', u'description': u'Direct3D11 hardware ANGLE', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'D3D11_HW_ANGLE'}, {u'status': u'available', u'description': u'GPU Process', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'GPU_PROCESS'}]}
- info: {u'AzureContentBackend (UI Process)': u'skia', u'AzureCanvasBackend (UI Process)': u'skia', u'ApzWheelInput': 1, u'AzureFallbackCanvasBackend (UI Process)': u'cairo', u'AzureCanvasAccelerated': 0, u'AzureCanvasBackend': u'Direct2D 1.1', u'AzureContentBackend': u'Direct2D 1.1'}
- isGPU2Active: False
- numAcceleratedWindows: 1
- numTotalWindows: 1
- webgl2Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 5500 Direct3D11 vs_5_0 ps_5_0)
- webglRenderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 5500 Direct3D11 vs_5_0 ps_5_0)
- windowLayerManagerRemote: True
- windowLayerManagerType: Direct3D 11
Modified Preferences
Misc
- User JS: No
- Accessibility: No
"32-bit" is the standard install.
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
Question owner
Only one shows up on the screen when I do that.
54aa6940-c2b3-4f33-b61c-006d24abef53
that was supposedly at 4:48 AM (it is not 5:31 PM).
The problems I posted about has occurred since then, today, and no "crash report" appears about that on my screen.
Question owner
I guess technically the problem is not a "crash", but a malfunction. That woul explain why it did not show up in the about:crashes report.
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.
Question owner
The one I listed in my reply was one not submitted. The ones that were submitted (if more were) I cannot make visible by clicking on anything, as far as I know.
I just clicked on the one report I included above, and now I hit the back arrow. Here is a copy and paste, then file saved to MS Paint.
bp-089bf374-bae2-42ec-b2b4-644410170602 Signature: `anonymous namespace::MessageEventRunnable::DispatchDOMEvent
This is for Sumo's Related Bugs 1286904 NEW --- Crash in `anonymous namespace::MessageEventRunnable::DispatchDOMEvent
I called for more help.
Question owner
I don't know what your last message means, FredMcD.
Question owner
Are you saying I should call someone? Whom?
I called others to come and help.