hi, can you please provide an id of a submitted crash report?

I've sent in lots (but just a few with failsafe start).

This should be one: bp-4d1ae201-7ded-4175-b415-6c30c0190224

See this thread:

• /questions/1251418 Firefox crashes on close

Are you using "Clear history when Firefox closes"?

Try to clear "offline website data" once. Remove the checkmark on all items except "offline website data".

• History -> "Clear Recent History"
• https://support.mozilla.org/en-US/kb/delete-browsing-search-download-history-firefox

Ok. So clearing out my cached cookies helped. But now, the problem is back, exactly the same, as I just reported in bp-2be96721-a520-4c6f-be6b-b2b4f0190312.

Since I get logged out of a heck of a lot of websites, clearing my cookie-cache-etc, every two weeks, doesn't really seem like a good solution....

Product Firefox Release Channel release Version 65.0.2 Build ID 20190225143501 (2019-02-25)

bp-2be96721-a520-4c6f-be6b-b2b4f0190312 Signature: AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

Crash Reason EXCEPTION_BREAKPOINT

System Memory Use Percentage 20

mbae.dll = Malwarebytes Anti-Exploit

This is for Sumo's Related Bugs 1524200 REOPENED --- Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

1507171 RESOLVED FIXED Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

1426941 RESOLVED INCOMPLETE Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

1404105 RESOLVED FIXED Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize,sanitize.js: Sanitize on shutdown

Update Malwarebytes. If the problem continues, disable it.

With malwarebytes service disabled.

bp-4ed277c9-991a-497d-a6ac-1bf920190313

bp-4ed277c9-991a-497d-a6ac-1bf920190313

Same as above but Malwarebytes not listed.

Are your settings set to clear history when Firefox closes?

Nope.

This is basically a hang with clearing some data during shutdown. This hang times out and there is automatically a crash forced.

You can read more about this issue in these two bug reports.

• Bug 1529301 - GetUsage takes too much time on shutdown
• Bug 1524200 - Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html)

theque42 said

I can start Firefox in Safe Mode, and just let the front page load and then close. This will, 100% of times, close a few Firefox processes, but the master process and a few child processes hang...with 12-25% load (according to sys-internals process explorer), for about a minute. Then the crash-reporter shows up to tell me FF crashed.

Your Extensions, Be Aplenty:

• Auto Reload Tab 0.5
• Avast Online Security 18.4.140
• Flash Block (Plus) 0.1.9
• gnu_terry_pratchett 0.4
• IDND 2.1
• IPvFoo 1.42
• JavaScript QR Code 1.5.7
• Kee 2.5.6
• Privacy Badger 2019.2.19
• ScriptSafe 1.0.9.8
• uBlock Origin 1.18.4
• Video DownloadHelper 7.3.5
• Viralgranskarens varningslista 0.1.2
• YouTube Download Plus 2.0.9
• Adblock Plus - free ad blocker 3.4.3 (Inactive)
• Add-on Compatibility Reporter 2.2.4 (Inactive)
• Download Status Bar 15.0.0.1 (Inactive)
• Facebook AdBlock 1.5.2 (Inactive)
• HTTPS Everywhere 2017.10.24 (Inactive)
• I don't care about cookies 2.9.6 (Inactive)
• JavaScript Toggle On and Off 0.2.2 (Inactive)
• Link Cleaner 1.5 (Inactive)
• Modify Headers 0.7.1.1.1-signed.1-signed (Inactive)
• NoScript 10.2.1 (Inactive)
• Password Exporter 1.3.4 (Inactive)
• Privatkopiera 0.1.9 (Inactive)
• User-Agent Switcher 0.1.8 (Inactive)

I know you said you did Safe Mode, but it's possible one or more Extensions could still be running even when Disabled or when FF is closed. Mainly, some of the Download Managers.

You need to check Task Manager closely to see. Other than that:

Please do the following:

Click on the Windows icon 'Start' (bottom-left) and in the right column, bottom, click on Run. Enter in:

...Wait until the green bar loads and disappears, then click "Save All Information".
Post back here in the Forum, just these information parts, under these three Headers:

~Pj

I'll try to get the logs. But its worth mentioning that I've had the same problem on another laptop(2), and one of them had a lot fewer addons(like no dl-mgrs).

Would a "full dump" from process explorer be of any help?

Did one while waiting for this crashdump reporter..

https://crash-stats.mozilla.org/report/index/c5282ba2-4f47-460d-af1c-5226d0190406

The logs from dxDiag

---

https://pastebin.com/x8uW2ehX

theque42 said

https://crash-stats.mozilla.org/report/index/c5282ba2-4f47-460d-af1c-5226d0190406

bp-c5282ba2-4f47-460d-af1c-5226d0190406 Signature: AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

Crash Reason EXCEPTION_BREAKPOINT

This is for Sumo's Related Bugs 1524200 REOPENED --- Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

1507171 RESOLVED FIXED Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

1426941 RESOLVED INCOMPLETE Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown

1404105 RESOLVED FIXED Crash in AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize,sanitize.js: Sanitize on shutdown

Bug 1524200 They have been working on this for several months, since v65 and while they created several patches, it keeps coming back.

Are you clearing history?

[v57+] Places Maintenance is built into Firefox.

Type about:support<enter> in the address bar.

You will find Places Database near the bottom. Press the Verify Integrity button.

When done, copy and post the results here.

No, I dont clear history. --- > 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 5120KiB + The database has been vacuumed + Final database size is 5120KiB > Task: stats + Places.sqlite size is 5120KiB + Favicons.sqlite size is 5760KiB + pragma_user_version is 52 + pragma_page_size is 32768 + pragma_cache_size is -2048 + pragma_journal_mode is wal + pragma_synchronous is 1 + History can store a maximum of 89981 unique pages + Table moz_places has 4369 records + Table moz_historyvisits has 4982 records + Table moz_inputhistory has 43 records + Table moz_hosts has 0 records + Table moz_bookmarks has 1885 records + Table moz_keywords has 5 records + Table sqlite_sequence has 1 records + Table moz_anno_attributes has 5 records + Table moz_annos has 255 records + Table moz_items_annos has 116 records + Table sqlite_stat1 has 20 records + Table moz_bookmarks_deleted has 0 records + Table moz_meta has 6 records + Table moz_origins has 1182 records + Index sqlite_autoindex_moz_inputhistory_1 + Index sqlite_autoindex_moz_hosts_1 + Index sqlite_autoindex_moz_keywords_1 + Index sqlite_autoindex_moz_anno_attributes_1 + Index sqlite_autoindex_moz_bookmarks_deleted_1 + Index sqlite_autoindex_moz_origins_1 + 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_bookmarks_itemindex + Index moz_bookmarks_parentindex + Index moz_bookmarks_itemlastmodifiedindex + Index moz_places_url_hashindex + Index moz_places_guid_uniqueindex + Index moz_bookmarks_guid_uniqueindex + Index moz_annos_placeattributeindex + Index moz_items_annos_itemattributeindex + Index moz_keywords_placepostdata_uniqueindex + Index moz_bookmarks_dateaddedindex + Index moz_places_originidindex > Task: _refreshUI