X
Tap here to go to the mobile version of the site.

Support Forum

Since updating to Ver. 62 the Crash Reporter keeps appearing every time I quit Firefox - Why?

Posted

Since the upgrade to Ver 62 was applied every time I launch Firefox, use it for any length of time then quit it successfully, the crash reporter appears. I have changed nothing else on the computer - as far as installation of software is concerned. I have not loaded or used anything browser related that I was not using before the new version of Firefox was loaded. I am getting fed up with this string of Crash Reporter windows appearing after every trip to the browser from my email client or anywhere else. If I knew how to turn it off, I would but then I would not be able to send a report if Firefox was to genuinely crash; something that rarely happens but is not unknown. My praiseworthy experience of Firefox over many years since previously using Netscape Navigator is being soured by this behaviour.

Since the upgrade to Ver 62 was applied every time I launch Firefox, use it for any length of time then quit it successfully, the crash reporter appears. I have changed nothing else on the computer - as far as installation of software is concerned. I have not loaded or used anything browser related that I was not using before the new version of Firefox was loaded. I am getting fed up with this string of Crash Reporter windows appearing after every trip to the browser from my email client or anywhere else. If I knew how to turn it off, I would but then I would not be able to send a report if Firefox was to genuinely crash; something that rarely happens but is not unknown. My praiseworthy experience of Firefox over many years since previously using Netscape Navigator is being soured by this behaviour.

Additional System Details

Installed Plug-ins

  • Shockwave Flash 27.0 r0

Application

  • Firefox 62.0
  • User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:62.0) Gecko/20100101 Firefox/62.0
  • Support URL: https://support.mozilla.org/1/firefox/62.0/WINNT/en-US/

Extensions

  • IDM Integration Module 6.31.2 (mozilla_cc3@internetdownloadmanager.com)
  • Adobe Acrobat 18.0.2 (web2pdfextension.17@acrobat.adobe.com) (Inactive)
  • IDM integration 6.27.7 (mozilla_cc2@internetdownloadmanager.com) (Inactive)

Javascript

  • incrementalGCEnabled: True

Graphics

  • adapterDescription: Intel(R) HD Graphics Family
  • adapterDescription2: NVIDIA NVS 4200M
  • adapterDeviceID: 0x0126
  • adapterDeviceID2: 0x1057
  • adapterDrivers: igdumd64 igd10umd64 igd10umd64 igdumdx32 igd10umd32 igd10umd32
  • adapterDrivers2: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
  • adapterRAM: Unknown
  • adapterRAM2: 1024
  • adapterSubsysID: 21d117aa
  • adapterSubsysID2: 21d117aa
  • adapterVendorID: 0x8086
  • adapterVendorID2: 0x10de
  • contentUsesTiling: True
  • crashGuards: []
  • direct2DEnabled: False
  • direct2DEnabledMessage: [u'tryNewerDriver', u'X.X.X.2342']
  • directWriteEnabled: True
  • directWriteVersion: 6.2.9200.22164
  • driverDate: 3-6-2011
  • driverDate2: 11-5-2015
  • driverVersion: 8.15.10.2321
  • driverVersion2: 10.18.13.5445
  • 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'blacklisted', u'description': u'Direct3D11 Compositing', u'log': [{u'status': u'available', u'type': u'default'}, {u'status': u'blacklisted', u'message': u'#BLOCKLIST_FEATURE_FAILURE_BUG_1018278', u'type': u'env'}], u'name': u'D3D11_COMPOSITING'}, {u'status': u'unavailable', u'description': u'Direct2D', u'log': [{u'status': u'unavailable', u'message': u'Direct2D requires Direct3D 11 compositing', u'type': u'default'}], u'name': u'DIRECT2D'}, {u'status': u'disabled', u'description': u'Direct3D11 hardware ANGLE', u'log': [{u'status': u'unavailable', u'message': u'D3D11 compositing is disabled', u'type': u'default'}, {u'status': u'disabled', u'message': u'D3D11 compositing is disabled', u'type': u'env'}], u'name': u'D3D11_HW_ANGLE'}, {u'status': u'blacklisted', u'description': u'GPU Process', u'log': [{u'status': u'available', u'type': u'default'}, {u'status': u'blacklisted', u'message': u'#BLOCKLIST_FEATURE_FAILURE_BUG_1018278', u'type': u'env'}], u'name': u'GPU_PROCESS'}, {u'status': u'unavailable', u'description': u'WebRender', u'log': [{u'status': u'opt-in', u'message': u'WebRender is an opt-in feature', u'type': u'default'}, {u'status': u'unavailable', u'message': u'ANGLE is disabled', u'type': u'runtime'}], u'name': u'WEBRENDER'}, {u'status': u'available', u'description': u'Off Main Thread Painting', u'log': [{u'status': u'available', u'type': u'default'}], u'name': u'OMTP'}]}
  • info: {u'ApzWheelInput': 1, u'ApzDragInput': 1, u'ApzKeyboardInput': 1, u'ApzAutoscrollInput': 1, u'AzureFallbackCanvasBackend': u'cairo', u'AzureCanvasAccelerated': 0, u'AzureCanvasBackend': u'skia', u'AzureContentBackend': u'skia'}
  • isGPU2Active: False
  • numAcceleratedWindows: 0
  • numAcceleratedWindowsMessage: [u'tryNewerDriver', u'X.X.X.2342']
  • numTotalWindows: 1
  • offMainThreadPaintEnabled: True
  • offMainThreadPaintWorkerCount: 1
  • usesTiling: False
  • webgl1DriverExtensions: GL_ANGLE_client_arrays GL_ANGLE_depth_texture GL_ANGLE_framebuffer_blit GL_ANGLE_framebuffer_multisample GL_ANGLE_instanced_arrays GL_ANGLE_lossy_etc_decode GL_ANGLE_pack_reverse_row_order GL_ANGLE_program_cache_control GL_ANGLE_request_extension GL_ANGLE_robust_client_memory GL_ANGLE_texture_compression_dxt3 GL_ANGLE_texture_compression_dxt5 GL_ANGLE_texture_usage GL_ANGLE_translated_shader_source GL_CHROMIUM_bind_generates_resource GL_CHROMIUM_bind_uniform_location GL_CHROMIUM_color_buffer_float_rgb GL_CHROMIUM_color_buffer_float_rgba GL_CHROMIUM_copy_compressed_texture GL_CHROMIUM_copy_texture GL_CHROMIUM_sync_query GL_EXT_blend_minmax GL_EXT_color_buffer_half_float GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_disjoint_timer_query GL_EXT_draw_buffers GL_EXT_frag_depth GL_EXT_map_buffer_range GL_EXT_occlusion_query_boolean GL_EXT_read_format_bgra GL_EXT_robustness GL_EXT_sRGB GL_EXT_shader_texture_lod GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc_srgb GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_EXT_texture_rg GL_EXT_texture_storage GL_EXT_unpack_subimage GL_KHR_debug GL_KHR_robust_buffer_access_behavior GL_NV_EGL_stream_consumer_external GL_NV_fence GL_NV_pack_subimage GL_NV_pixel_buffer_object GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth32 GL_OES_element_index_uint GL_OES_get_program_binary GL_OES_mapbuffer GL_OES_packed_depth_stencil GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_surfaceless_context GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_array_object
  • webgl1Extensions: ANGLE_instanced_arrays EXT_blend_minmax EXT_color_buffer_half_float EXT_frag_depth EXT_sRGB EXT_shader_texture_lod EXT_texture_filter_anisotropic EXT_disjoint_timer_query OES_element_index_uint OES_standard_derivatives OES_texture_float OES_texture_float_linear OES_texture_half_float OES_texture_half_float_linear OES_vertex_array_object WEBGL_color_buffer_float WEBGL_compressed_texture_s3tc WEBGL_compressed_texture_s3tc_srgb WEBGL_debug_renderer_info WEBGL_debug_shaders WEBGL_depth_texture WEBGL_draw_buffers WEBGL_lose_context
  • webgl1Renderer: Google Inc. -- ANGLE (Software Adapter Direct3D11 vs_5_0 ps_5_0)
  • webgl1Version: OpenGL ES 2.0 (ANGLE 2.1.0.595ccab4acc3)
  • webgl1WSIInfo: EGL_VENDOR: Google Inc. (adapter LUID: 0000000000000000) EGL_VERSION: 1.4 (ANGLE 2.1.0.595ccab4acc3) EGL_EXTENSIONS: EGL_EXT_create_context_robustness EGL_ANGLE_d3d_texture_client_buffer EGL_ANGLE_query_surface_pointer EGL_ANGLE_window_fixed_size EGL_ANGLE_keyed_mutex EGL_ANGLE_surface_orientation EGL_NV_post_sub_buffer EGL_KHR_create_context EGL_EXT_device_query EGL_KHR_image EGL_KHR_image_base EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_get_all_proc_addresses EGL_KHR_stream EGL_KHR_stream_consumer_gltexture EGL_NV_stream_consumer_gltexture_yuv EGL_ANGLE_flexible_surface_compatibility EGL_ANGLE_stream_producer_d3d_texture EGL_ANGLE_create_context_webgl_compatibility EGL_CHROMIUM_create_context_bind_generates_resource EGL_EXT_pixel_format_float EGL_KHR_surfaceless_context EGL_ANGLE_display_texture_share_group EGL_ANGLE_create_context_client_arrays EGL_ANGLE_program_cache_control EGL_ANGLE_robust_resource_initialization EGL_ANGLE_create_context_extensions_enabled EGL_EXTENSIONS(nullptr): EGL_EXT_client_extensions EGL_EXT_platform_base EGL_EXT_platform_device EGL_ANGLE_platform_angle EGL_ANGLE_platform_angle_d3d EGL_ANGLE_device_creation EGL_ANGLE_device_creation_d3d11 EGL_ANGLE_experimental_present_path EGL_KHR_client_get_all_proc_addresses
  • webgl2DriverExtensions: -
  • webgl2Extensions: -
  • webgl2Renderer: WebGL creation failed: * Refused to create WebGL2 context because of blacklist entry: FEATURE_FAILURE_BUG_1018278
  • webgl2Version: -
  • webgl2WSIInfo: -
  • windowLayerManagerRemote: True
  • windowLayerManagerType: Basic
  • windowUsingAdvancedLayers: False

Modified Preferences

Misc

  • User JS: No
  • Accessibility: No
cor-el
  • Top 10 Contributor
  • Moderator
17415 solutions 157316 answers

Note that the System Details list shows an outdated plugin.

  • Shockwave Flash 27.0 r0

You can download the latest Flash player plugin for Firefox on this page.


If you have submitted crash reports then please post the IDs of one or more recent crash reports that start with "bp-".

  • bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

You can find the report ID of recent crash reports "on the "Help -> Troubleshooting Information" (about:support) page".

  • click the "All Crash Reports" button on this page to open the about:crashes page and see all crash reports.

Alternatively you can open about:crashes via the location/address bar.

See also:

Note that the System Details list shows an outdated plugin. *Shockwave Flash 27.0 r0 You can download the latest Flash player plugin for Firefox on this page. *https://get.adobe.com/flashplayer/otherversions/ ---- If you have submitted crash reports then please post the IDs of one or more recent crash reports that start with "bp-". *bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx You can find the report ID of recent crash reports "on the "Help -> Troubleshooting Information" (about:support) page". *click the "All Crash Reports" button on this page to open the <b>about:crashes</b> page and see all crash reports. Alternatively you can open about:crashes via the location/address bar. See also: *https://support.mozilla.org/en-US/kb/Mozilla+Crash+Reporter
jscher2000
  • Top 10 Contributor
8635 solutions 70627 answers

Hopefully the crash reports will help point to the culprit.

If you set Firefox to clear history automatically when you close it, that might sometimes cause an issue where Firefox doesn't close down within the usual time (and a watchdog process "kills" Firefox and triggers the crash dialog).

Also, why close Firefox so often? You can minimize the Firefox window to save time the next time you launch a link or want to browse. That would at least reduce the number of times per day you have this issue.

Hopefully the crash reports will help point to the culprit. If you set Firefox to clear history automatically when you close it, that might sometimes cause an issue where Firefox doesn't close down within the usual time (and a watchdog process "kills" Firefox and triggers the crash dialog). Also, why close Firefox so often? You can minimize the Firefox window to save time the next time you launch a link or want to browse. That would at least reduce the number of times per day you have this issue.

Question owner

Dear cor-el,

Many thanks for the link to update my Flash Player. Sadly it seems to have made no difference. I have investigated a little further and discovered the following - which you probably know anyway, from the crash reports. When Firefox is running there appear to be three instances running as shown in my Process Explorer, I am attaching .jpegs grabbed during my 'study' to show them and what they are seen to be doing. When I shut down Firefox, two of them disappear very quickly leaving one, in the fourth image, which stays 'live' for about 1 minute before the Crash Reporter springs to life as the Firefox.exe instance disappears. I guess that you will understand why this remaining 'instance' doesn't shut down.

I hope that this helps.

Dear cor-el, Many thanks for the link to update my Flash Player. Sadly it seems to have made no difference. I have investigated a little further and discovered the following - which you probably know anyway, from the crash reports. When Firefox is running there appear to be three instances running as shown in my Process Explorer, I am attaching .jpegs grabbed during my 'study' to show them and what they are seen to be doing. When I shut down Firefox, two of them disappear very quickly leaving one, in the fourth image, which stays 'live' for about 1 minute before the Crash Reporter springs to life as the Firefox.exe instance disappears. I guess that you will understand why this remaining 'instance' doesn't shut down. I hope that this helps.
cor-el
  • Top 10 Contributor
  • Moderator
17415 solutions 157316 answers

It is quite normal to see three or more Firefox processes running.

  • one process for the main Firefox thread (user interface)
  • one or more content processes set via dom.ipc.processCount
    Options/Preferences -> General -> Performance
    remove checkmark: [ ] "Use recommended performance settings"
  • one process for the compositor thread (Windows;graphics)

You can find the current multi-process state on the Troubleshooting Information (about:support) page.

  • "Help -> Troubleshooting Information" -> "Application Basics":
    Multiprocess Windows
    Web Content Processes

Did you submit any crash reports (see the last part of my above reply)?

If that is the case then please post the IDs of one or more recent crash reports that start with "bp-".

  • bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

If a line on the about:crashes page doesn't start with "bp-" then you can click the line to submit the report and the link will be updated and gets a "bp-" prefix if the report is submitted successfully.

  • please do not add the "bp-" prefix yourself

See also:

It is quite normal to see three or more Firefox processes running. *one process for the main Firefox thread (user interface) *one or more content processes set via dom.ipc.processCount<br>Options/Preferences -> General -> Performance<br>remove checkmark: [ ] "Use recommended performance settings" *one process for the compositor thread (Windows;graphics) You can find the current multi-process state on the Troubleshooting Information (about:support) page. *"Help -> Troubleshooting Information" -> "Application Basics":<br>Multiprocess Windows<br>Web Content Processes ---- Did you submit any crash reports (see the last part of my above reply)? If that is the case then please post the IDs of one or more recent crash reports that start with "bp-". *bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx If a line on the about:crashes page doesn't start with "bp-" then you can click the line to submit the report and the link will be updated and gets a "bp-" prefix if the report is submitted successfully. *please do not add the "bp-" prefix yourself See also: *https://support.mozilla.org/en-US/kb/Mozilla+Crash+Reporter

Question owner

bp-8c8864ae-1e44-4edd-b4b7-548980180912

Is the latest in a long line of them.

bp-8c8864ae-1e44-4edd-b4b7-548980180912 Is the latest in a long line of them.
jscher2000
  • Top 10 Contributor
8635 solutions 70627 answers

This crash report indicates:

Signature: AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

This is the issue I mentioned before where sometimes the "Clear history when Firefox closes" feature hangs up. I don't remember the possible reasons that happens, but you could try manually deleting history you want to clear before shutdown to see whether that ends the issue.

The "Clear Recent History" feature can be accessed using either:

  • Libary menu button > History > Clear Recent History
  • Ctrl+Shift+Delete

Make sure you expand the "Details" panel and only clear the categories you want to clear. (In particular, don't clear "Site Preferences" which are permissions/exceptions you've set, and may include zoom levels and download folders.)

This crash report indicates: Signature: AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown This is the issue I mentioned before where sometimes the "Clear history when Firefox closes" feature hangs up. I don't remember the possible reasons that happens, but you could try manually deleting history you want to clear before shutdown to see whether that ends the issue. The "Clear Recent History" feature can be accessed using either: * Libary menu button > History > Clear Recent History * Ctrl+Shift+Delete Make sure you expand the "Details" panel and only clear the categories you want to clear. (In particular, don't clear "Site Preferences" which are permissions/exceptions you've set, and may include zoom levels and download folders.)
dkon1000 1 solutions 14 answers

I have noticed the exact same problem after upgrading to V62. The process stays running after closing until eventually it times out and the crash reporter window appears. I have disabled all addons and it makes no difference. Would be great if someone has some ideas why this is happening

I have noticed the exact same problem after upgrading to V62. The process stays running after closing until eventually it times out and the crash reporter window appears. I have disabled all addons and it makes no difference. Would be great if someone has some ideas why this is happening
jscher2000
  • Top 10 Contributor
8635 solutions 70627 answers

Hi dkon1000, do you have crash report IDs that might shed light on the source of the problem?

Generally speaking, the thing Firefox does at shutdown which seems to cause the most hangups is clearing data ("Clear history when Firefox closes").

Hi dkon1000, do you have crash report IDs that might shed light on the source of the problem? Generally speaking, the thing Firefox does at shutdown which seems to cause the most hangups is clearing data ("Clear history when Firefox closes").
dkon1000 1 solutions 14 answers

6ab4c469-1a6b-4271-9db5-633040180927

6ab4c469-1a6b-4271-9db5-633040180927
dkon1000 1 solutions 14 answers

I do not have the option selected to clear history when firefox closes

I do not have the option selected to clear history when firefox closes
jscher2000
  • Top 10 Contributor
8635 solutions 70627 answers

dkon1000 said

6ab4c469-1a6b-4271-9db5-633040180927

dkon1000 said

I do not have the option selected to clear history when firefox closes

https://crash-stats.mozilla.com/report/index/6ab4c469-1a6b-4271-9db5-633040180927

This is reported as a "Sanitize on shutdown" crash:

Signature: AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

I wonder if there is some other setting that might trigger that?

''dkon1000 [[#answer-1159031|said]]'' <blockquote> 6ab4c469-1a6b-4271-9db5-633040180927 </blockquote> ''dkon1000 [[#answer-1159033|said]]'' <blockquote> I do not have the option selected to clear history when firefox closes </blockquote> https://crash-stats.mozilla.com/report/index/6ab4c469-1a6b-4271-9db5-633040180927 This is reported as a "Sanitize on shutdown" crash: Signature: AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown I wonder if there is some other setting that might trigger that?
dkon1000 1 solutions 14 answers

What might cause that to occur. It definitely started with V62

What might cause that to occur. It definitely started with V62

Question owner

It is still happening, I am now on 62.0.2. I have cleared the history I want to clear. I have tried setting the 'clear history' to Do NOT, I have even attempted to set to NOT send crash reports - and it still does exactly the same as when I first asked this question. If I attempt to restart Firefox during the period when that last Firefox.exe is running it says that Firefox must be closed before it can restart: it closes it and relaunches - and the crash reporter appears again! I have never had this problem since pre-Firefox history until now. Why should the 'clear history' routine hang when it isn't supposed to be running?

It is still happening, I am now on 62.0.2. I have cleared the history I want to clear. I have tried setting the 'clear history' to Do NOT, I have even attempted to set to NOT send crash reports - and it still does exactly the same as when I first asked this question. If I attempt to restart Firefox during the period when that last Firefox.exe is running it says that Firefox must be closed before it can restart: it closes it and relaunches - and the crash reporter appears again! I have never had this problem since pre-Firefox history until now. Why should the 'clear history' routine hang when it isn't supposed to be running?

Question owner

Another version of Firefox (62.0.3) and still that d***d Crash Reporter follows every shut down after a successful browsing session. As I previously asked: why is the 'clear history' routine running when i have instructed it NOT to clear my history (I am quite happy to selectively do that myself)?

Another version of Firefox (62.0.3) and still that d***d Crash Reporter follows every shut down after a successful browsing session. As I previously asked: why is the 'clear history' routine running when i have instructed it NOT to clear my history (I am quite happy to selectively do that myself)?
jscher2000
  • Top 10 Contributor
8635 solutions 70627 answers

Hi MikeyJ, does it matter how long Firefox runs before you shut it down, or does this same problem occur even after a brief session?

The crash report signature mentions "Places Clients shutdown". Places is the database that stores history, downloads, and bookmarks.

There is a tool you can use to check whether the Places database is structurally sound:

Verify Integrity

The Troubleshooting Information page has a "Verify Integrity" button to do a little light maintenance on the Places database (where bookmarks and history are stored). You can open that using either

  • "3-bar" menu button > "?" Help > Troubleshooting Information
  • (menu bar) Help > Troubleshooting Information
  • type or paste about:support in the address bar and press Enter

Then scroll way down or use Find to search for Integrity in the Places Database section. At first, nothing will seem to happen, but then several seconds after clicking the button Firefox should report some diagnostic results below it.

Please copy/paste the results somewhere safe, then exit/restart Firefox to see whether it helped.

Hi MikeyJ, does it matter how long Firefox runs before you shut it down, or does this same problem occur even after a brief session? The crash report signature mentions "Places Clients shutdown". Places is the database that stores history, downloads, and bookmarks. There is a tool you can use to check whether the Places database is structurally sound: '''Verify Integrity''' The Troubleshooting Information page has a "Verify Integrity" button to do a little light maintenance on the Places database (where bookmarks and history are stored). You can open that using either * "3-bar" menu button > "?" Help > Troubleshooting Information * (menu bar) Help > Troubleshooting Information * type or paste about:support in the address bar and press Enter Then scroll way down or use Find to search for ''Integrity'' in the Places Database section. At first, nothing will seem to happen, but then several seconds after clicking the button Firefox should report some diagnostic results below it. Please copy/paste the results somewhere safe, then exit/restart Firefox to see whether it helped.

Question owner

Thank you for your suggestion which all ran as you described. Sadly it doesn't appear to have prevented the Crash Reporter appearing once more after about a minute from me closing Firefox. There is no difference between having Firefox open for a few minutes or a few hours: close, wait for a minute and there it is. I include the contents of the report here: > Task: checkIntegrity + The places.sqlite database is sane + The favicons.sqlite database is sane > Task: invalidateCaches + The caches have been invalidated > Task: checkCoherence + The database is coherent > Task: expire + Database cleaned up > Task: originFrecencyStats + Recalculated origin frecency stats > Task: vacuum + Initial database size is 10240KiB + The database has been vacuumed + Final database size is 10240KiB > Task: stats + Places.sqlite size is 10240KiB + Favicons.sqlite size is 7808KiB + pragma_user_version is 52 + pragma_page_size is 4096 + pragma_cache_size is -2048 + pragma_journal_mode is wal + pragma_synchronous is 1 + History can store a maximum of 123848 unique pages + Table moz_bookmarks has 5711 records + Table moz_keywords has 0 records + Table sqlite_sequence has 1 records + Table moz_annos has 1257 records + Table moz_anno_attributes has 6 records + Table moz_items_annos has 623 records + Table moz_places has 10513 records + Table moz_historyvisits has 11549 records + Table moz_inputhistory has 0 records + Table sqlite_stat1 has 17 records + Table moz_hosts has 0 records + Table moz_bookmarks_deleted has 5 records + Table moz_meta has 5 records + Table moz_origins has 1990 records + Index sqlite_autoindex_moz_keywords_1 + Index sqlite_autoindex_moz_anno_attributes_1 + Index sqlite_autoindex_moz_inputhistory_1 + Index sqlite_autoindex_moz_hosts_1 + Index sqlite_autoindex_moz_bookmarks_deleted_1 + Index sqlite_autoindex_moz_origins_1 + Index moz_bookmarks_itemindex + Index moz_bookmarks_parentindex + Index moz_bookmarks_itemlastmodifiedindex + Index moz_places_hostindex + Index moz_places_visitcount + Index moz_places_frecencyindex + Index moz_places_lastvisitdateindex + Index moz_historyvisits_placedateindex + Index moz_historyvisits_fromindex + Index moz_historyvisits_dateindex + Index moz_places_url_hashindex + Index moz_annos_placeattributeindex + Index moz_items_annos_itemattributeindex + Index moz_bookmarks_guid_uniqueindex + Index moz_places_guid_uniqueindex + Index moz_keywords_placepostdata_uniqueindex + Index moz_bookmarks_dateaddedindex + Index moz_places_originidindex > Task: _refreshUI

Thank you for your suggestion which all ran as you described. Sadly it doesn't appear to have prevented the Crash Reporter appearing once more after about a minute from me closing Firefox. There is no difference between having Firefox open for a few minutes or a few hours: close, wait for a minute and there it is. I include the contents of the report here: > Task: checkIntegrity + The places.sqlite database is sane + The favicons.sqlite database is sane > Task: invalidateCaches + The caches have been invalidated > Task: checkCoherence + The database is coherent > Task: expire + Database cleaned up > Task: originFrecencyStats + Recalculated origin frecency stats > Task: vacuum + Initial database size is 10240KiB + The database has been vacuumed + Final database size is 10240KiB > Task: stats + Places.sqlite size is 10240KiB + Favicons.sqlite size is 7808KiB + pragma_user_version is 52 + pragma_page_size is 4096 + pragma_cache_size is -2048 + pragma_journal_mode is wal + pragma_synchronous is 1 + History can store a maximum of 123848 unique pages + Table moz_bookmarks has 5711 records + Table moz_keywords has 0 records + Table sqlite_sequence has 1 records + Table moz_annos has 1257 records + Table moz_anno_attributes has 6 records + Table moz_items_annos has 623 records + Table moz_places has 10513 records + Table moz_historyvisits has 11549 records + Table moz_inputhistory has 0 records + Table sqlite_stat1 has 17 records + Table moz_hosts has 0 records + Table moz_bookmarks_deleted has 5 records + Table moz_meta has 5 records + Table moz_origins has 1990 records + Index sqlite_autoindex_moz_keywords_1 + Index sqlite_autoindex_moz_anno_attributes_1 + Index sqlite_autoindex_moz_inputhistory_1 + Index sqlite_autoindex_moz_hosts_1 + Index sqlite_autoindex_moz_bookmarks_deleted_1 + Index sqlite_autoindex_moz_origins_1 + Index moz_bookmarks_itemindex + Index moz_bookmarks_parentindex + Index moz_bookmarks_itemlastmodifiedindex + Index moz_places_hostindex + Index moz_places_visitcount + Index moz_places_frecencyindex + Index moz_places_lastvisitdateindex + Index moz_historyvisits_placedateindex + Index moz_historyvisits_fromindex + Index moz_historyvisits_dateindex + Index moz_places_url_hashindex + Index moz_annos_placeattributeindex + Index moz_items_annos_itemattributeindex + Index moz_bookmarks_guid_uniqueindex + Index moz_places_guid_uniqueindex + Index moz_keywords_placepostdata_uniqueindex + Index moz_bookmarks_dateaddedindex + Index moz_places_originidindex > Task: _refreshUI
dkon1000 1 solutions 14 answers

For what its worth I managed to finally solve the problem although I still don't know what was the source of the issue with this release. I used the Firefox sync feature to sync all of my bookmarks online. Then I uninstalled Firefox and rebooted my computer. Downloaded a new copy of Firefox and when installing it indicated that a previous version had existed in the past. I selected the options to do a completely refreshed new install (a copy of my old profile was saved to my desktop during the install). After everything was running again I entered my sync account details so all my bookmarks reappeared. Then add the few addons that I actually use and everything now seems to be working without any crashes on closing. After many years of upgrades perhaps I just needed a clean install

For what its worth I managed to finally solve the problem although I still don't know what was the source of the issue with this release. I used the Firefox sync feature to sync all of my bookmarks online. Then I uninstalled Firefox and rebooted my computer. Downloaded a new copy of Firefox and when installing it indicated that a previous version had existed in the past. I selected the options to do a completely refreshed new install (a copy of my old profile was saved to my desktop during the install). After everything was running again I entered my sync account details so all my bookmarks reappeared. Then add the few addons that I actually use and everything now seems to be working without any crashes on closing. After many years of upgrades perhaps I just needed a clean install
jscher2000
  • Top 10 Contributor
8635 solutions 70627 answers

A Refresh can work wonders, too.

A Refresh can work wonders, too.
FredMcD
  • Top 10 Contributor
4224 solutions 58953 answers

dkon1000 said

For what its worth I managed to finally solve the problem

That was very good work. Well done. Please flag your last post as Solved Problem so others will know.

''dkon1000 [[#answer-1160970|said]]'' <blockquote> For what its worth I managed to finally solve the problem </blockquote> That was very good work. Well done. Please flag your last post as '''Solved Problem''' so others will know.
dkon1000 1 solutions 14 answers

Would love to do that but can't figure out how. Sorry. Still a bit new with all of this

Would love to do that but can't figure out how. Sorry. Still a bit new with all of this