hello, could you provide your latest few submitted crash reports? please enter about:crashes into the location bar, copy the latest few report ids from there starting with bp- & paste them here into a forum reply. this will give us a better understanding what may be triggering those crashes.

Since 02/19/2019 I have submitted 14 crash reports, and they are still happening!

Mozilla Crash Reports Search Sign in Quick Navigation • Select Product • • Select Version: • • Report: • Documentation | File a bug | Super Search Firefox 65.0.1 Crash Report [@ shutdownhang | mozilla::net::nsStandardURL::SetSpecWithEncoding ] Search Mozilla Support for this signature How to read this crash report ID: c56be918-fe78-401f-b92a-c80bb0190221 Signature: shutdownhang | mozilla::net::nsStandardURL::SetSpecWithEncoding • Details • Metadata • Bugzilla • Modules • Raw Dump • Extensions • Telemetry Environment • Correlations Signature shutdownhang | mozilla::net::nsStandardURL::SetSpecWithEncoding More Reports Search

UUID c56be918-fe78-401f-b92a-c80bb0190221 Date Processed 2019-02-21 22:07:23 UTC Uptime 908 seconds (15 minutes and 8 seconds) Last Crash 1,715 seconds before submission (28 minutes and 35 seconds) Install Age 366,265 seconds since version was first installed (4 days, 5 hours and 44 minutes) Install Time 2019-02-17 16:19:12 Product Firefox Release Channel release Version 65.0.1 Build ID 20190211233335 (2019-02-11) Buildhub data

OS Windows 8.1 OS Version 6.3.9600 Build Architecture amd64 CPU Info family 6 model 69 stepping 1 CPU Count 4 Adapter Vendor ID Intel Corporation (0x8086) Adapter Device ID Haswell-ULT Integrated Graphics Controller (0x0a26) Startup Crash False MOZ_CRASH Reason (Sanitized) MOZ_CRASH(Shutdown hanging before starting.) Crash Reason EXCEPTION_BREAKPOINT Crash Address 0x7ffbfb721d5c Total Virtual Memory 140,737,488,224,256 bytes (140.74 TB) Available Virtual Memory 140,734,741,200,896 bytes (140.73 TB) Available Page File 13,003,399,168 bytes (13 GB) Available Physical Memory 4,293,341,184 bytes (4.29 GB) System Memory Use Percentage 49 EMCheckCompatibility False App Notes FP(D00-L1000-W00001000-T000) DWrite? DWrite+ WR? WR- OMTP? OMTP+3 Processor Notes processor_ip-172-31-35-4_us-west-2_compute_internal_8; Processor2015 Crashing Thread (0) Frame Module Signature Source Trust 0 xul.dll mozilla::net::nsStandardURL::SetSpecWithEncoding(nsTSubstring<char> const&, mozilla::Encoding const*) netwerk/base/nsStandardURL.cpp:1502 context 1 xul.dll mozilla::net::nsStandardURL::TemplatedMutator<mozilla::net::nsStandardURL>::Init(unsigned int, int, nsTSubstring<char> const&, char const*, nsIURI*, nsIURIMutator**) netwerk/base/nsStandardURL.h:372 cfi 2 xul.dll nsresult std::_Func_impl_no_alloc<`lambda at z:/build/build/src/obj-firefox/dist/include\nsIURIMutator.h:444:10', nsresult, nsIURIMutator*>::_Do_call(class nsIURIMutator**) cfi 3 xul.dll static nsresult mozilla::net::NewURI(const class nsTSubstring<char>& const, const char*, class nsIURI*, int, class nsIURI**) netwerk/protocol/http/nsHttpHandler.cpp:139 cfi 4 xul.dll mozilla::net::nsIOService::NewURI(nsTSubstring<char> const&, char const*, nsIURI*, nsIURI**) netwerk/base/nsIOService.cpp:658 cfi 5 xul.dll static nsresult `anonymous namespace'::GetPrincipalFromOrigin(const class nsTSubstring<char>& const, class nsIPrincipal**) extensions/cookie/nsPermissionManager.cpp:199 cfi 6 xul.dll nsPermissionManager::GetAllWithTypePrefix(nsTSubstring<char> const&, nsTArray<RefPtr<nsIPermission> >&) extensions/cookie/nsPermissionManager.cpp:2527 cfi 7 xul.dll nsPermissionManager::GetEnumerator(nsISimpleEnumerator**) extensions/cookie/nsPermissionManager.cpp:2487 cfi 8 xul.dll XPTC__InvokebyIndex xpcom/reflect/xptcall/md/win32/xptcinvoke_asm_x86_64.asm:97 cfi 9 @0x69c8dda6c7 cfi 10 xul.dll XPCWrappedNative::CallMethod(XPCCallContext&, XPCWrappedNative::CallMode) js/xpconnect/src/XPCWrappedNative.cpp:1182 scan 11 xul.dll static bool XPC_WN_GetterSetter(struct JSContext*, unsigned int, union JS::Value*) js/xpconnect/src/XPCWrappedNativeJSOps.cpp:988 cfi 12 @0x3cce4b37f67 cfi 13 xul.dll trunc scan Show other threads Mozilla Crash Reports - Powered by Socorro - All dates are UTC • Privacy Policy </p>

Mozilla Crash Reports Search Sign in Quick Navigation • Select Product • • Select Version: • • Report: • Documentation | File a bug | Super Search Firefox 58.0.2 Crash Report [@ IPCError-browser | ShutDownKill ] Search Mozilla Support for this signature How to read this crash report ID: 591bd3be-f106-41ea-bcc8-753f60190221 Signature: IPCError-browser | ShutDownKill • Details • Metadata • Bugzilla • Modules • Raw Dump • Extensions • Telemetry Environment • Correlations Signature IPCError-browser | ShutDownKill More Reports Search

UUID 591bd3be-f106-41ea-bcc8-753f60190221 Date Processed 2019-02-21 22:08:58 UTC Uptime 1,064 seconds (17 minutes and 44 seconds) Install Age 1,273,476 seconds since version was first installed (2 weeks, 17 hours and 44 minutes) Install Time 2018-02-22 00:31:50 Product Firefox Release Channel release Version 58.0.2 Build ID 20180206200532 (2018-02-06) Buildhub data

OS Unknown OS Version Build Architecture CPU Info CPU Count 0 Adapter Vendor ID Intel Corporation (0x8086) Adapter Device ID Haswell-ULT Integrated Graphics Controller (0x0a26) Startup Crash False Process Type content (extension) Crash Reason None Crash Address None EMCheckCompatibility True App Notes FP(D00-L1000-W00001000-T000) AdapterVendorID: 0x8086, AdapterDeviceID: 0x0a26, AdapterSubsysID: 20548086, AdapterDriverVersion: 10.18.14.4332 D2D1.1? DWrite? DWrite+ D2D1.1+ WR? WR- OMTP? OMTP+ Processor Notes processor_ip-172-31-26-88_us-west-2_compute_internal_9; Processor2015; MDSW failed with 0: ERROR_NO_MINIDUMP_HEADER; non-integer value of "SecondsSinceLastCrash"; MDSW did not identify the crashing thread; exploitability information missing; no 'topmost_file' name because crash_info is missing; SignatureGenerationRule: CSignatureTool: No signature could be created because we do not know which thread crashed; SignatureIPCChannelError: Signature replaced with an IPC Channel Error, was: "EMPTY: no crashing thread identified; ERROR_NO_MINIDUMP_HEADER" Mozilla Crash Reports - Powered by Socorro - All dates are UTC • Privacy Policy

thanks, those reports show that you are running multiple ad-/content blockers at the same time which is a recipe for causing problems. please refresh firefox and then just stick to a single addon in this category - i'd recommend https://addons.mozilla.org/firefox/addon/ublock-origin/

I have been using Adblock Plus for years and have great faith in it so I removed uBlock Origin.

No change (actually I did not expect a change). FireFox still crashes on exit. Based on your comments and the history of uBlock Origin (and uBlock), I will consider it an undesirable Add-on.

I did note that, per Task Manager, FireFox was taking 65 or more seconds to close. My laptop is running FireFox 65.0.0 (I have been afraid to update it) and does not have this problem.

My first thought was to figure out how to replace 65.0.1 with 65.0.0, but it looks like Mozilla has "fixed" FireFox to prevent this.

Then I started comparing settings and found that on my desktop, Menu>Content Blocking>Cookies and Site Data was set to "Delete cookies and site data when FireFox is closed". I am not a fan of cookies and/or tracking. Removing this setting appears to have solved the problem.

Sadly, I have to assume that deleting cookies (and site data) is NOT strongly supported by Mozilla, therefore causing it to crash (maybe do other things in that 65+ seconds.

Thank you for your input. I'm sure FireFox will have more problems soon.

You can let the cookies expire when Firefox is closed to make them session cookies instead of using "Clear history when Firefox closes" to clear the cookies.

• Options/Preferences -> Privacy & Security
  Firefox will: "Use custom settings for history" -> Cookies: Keep until: "I close Firefox"

You can create an Allow exception to keep specific cookies.

You can set network.cookie.thirdparty.sessionOnly to true on the about:config page to make third-party cookies behave as session cookies that expire when Firefox is closed.

First, your full post did not come through in email.

Second, I can not find "Use custom settings for history" --> Cookies: Keep until: "I close Firefox".

Images attached.

BTW: 86% of cookies were persistent cookies (remain on a person's device after use). 14% were session cookies (removed after a person's browsing session has ended). The average cookie is set to expire after one to two years but some cookies were being set for as long at 10, 100 or even nearly 8000 years.

I can't wait that long.

Keep until would be "Delete cookies and site data when Firefox is closed" in the first screenshot. Using this choice you can create an allow exception for cookie you want to keep.

If you click the text in the second screenshot after "Firefox will" then you will find the "Use custom settings for history" choice that allow to inspect and modify individual choices.