Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Firefox processes don't stop for a minute after exiting, then crash announced.

  • 6 Antworten
  • 1 hat dieses Problem
  • 4 Aufrufe
  • Letzte Antwort von TyDraniu

more options

Dell 64 bit Precision workstation; Win 10 64 bit version 1803; Firefox 62.0 64 bit. In last few days Firefox starts and appears to run normally. Task Manager shows the Fiirefox app with 6 firefox.exe processes. When exited the app disappears, leaving 3 firefox.exe processes, one of which uses about 20% of CPU. After a minute or so they stop and the "Firefox crashed" box appears. Disabling all the addins doesn't change this behavior. Neither did uninstalling/reinstalling firefox, rebooting, etc. I would very much appreciate any suggestions!

Here are some crash reports:

bp-5ebdb396-8862-4ffe-8985-39f9b0180910 9/10/2018 12:11 PM bp-d76c8eed-9e4d-42db-96da-0bb220180910 9/9/2018 9:50 PM bp-e04c647a-5877-4f7e-9658-769be0180908 9/8/2018 4:41 PM bp-75a6f3de-eb4b-48ae-b8ca-47c0e0180908 9/8/2018 1:58 PM

Dell 64 bit Precision workstation; Win 10 64 bit version 1803; Firefox 62.0 64 bit. In last few days Firefox starts and appears to run normally. Task Manager shows the Fiirefox app with 6 firefox.exe processes. When exited the app disappears, leaving 3 firefox.exe processes, one of which uses about 20% of CPU. After a minute or so they stop and the "Firefox crashed" box appears. Disabling all the addins doesn't change this behavior. Neither did uninstalling/reinstalling firefox, rebooting, etc. I would very much appreciate any suggestions! Here are some crash reports: bp-5ebdb396-8862-4ffe-8985-39f9b0180910 9/10/2018 12:11 PM bp-d76c8eed-9e4d-42db-96da-0bb220180910 9/9/2018 9:50 PM bp-e04c647a-5877-4f7e-9658-769be0180908 9/8/2018 4:41 PM bp-75a6f3de-eb4b-48ae-b8ca-47c0e0180908 9/8/2018 1:58 PM

Alle Antworten (6)

more options

have you set firefox to clear some data on shut-down (history, cache)? it might have become to big to be purged within that 60 seconds after closing the app... you could try if manually deleting the unwanted entries (ctrl+shift+del) during a session improves things.

more options

Thank you for your response. Firefox is not set to clear history or cache when it exits.

more options

Signature:

  • Firefox 62.0 Crash Report [@ AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown ]

Is there any other data cleared via "Clear history when Firefox closes" when you close Firefox?

more options

Hi, we ask that as there is no information : Signature AsyncShutdownTimeout | Places Clients shutdown | sanitize.js: Sanitize on shutdown Something is cleaning out all the data that would let us know more of the issue.


Try please to go to the 3 Bar Menu --> Help --> Troubleshooting Information --> Down to the very bottom all most to Places Database and click on Verify Integrity

more options

Here's what Verify Integrity says: > 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 61440KiB + The database has been vacuumed + Final database size is 61440KiB > Task: stats + Places.sqlite size is 61440KiB + Favicons.sqlite size is 6656KiB + 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 149797 unique pages + Table moz_bookmarks has 938 records + Table moz_keywords has 5 records + Table sqlite_sequence has 1 records + Table moz_annos has 970 records + Table moz_anno_attributes has 7 records + Table moz_items_annos has 160 records + Table moz_places has 127267 records + Table moz_historyvisits has 209540 records + Table moz_inputhistory has 2 records + Table sqlite_stat1 has 19 records + Table moz_hosts has 0 records + Table moz_bookmarks_deleted has 0 records + Table moz_meta has 8 records + Table moz_origins has 10695 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_historyvisits_placedateindex + Index moz_historyvisits_fromindex + Index moz_historyvisits_dateindex + Index moz_places_lastvisitdateindex + 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

Does this suggest anything? Thanks!

more options

Try to clear the cache; I have had something like this when cache volume hit max.