Firefox 36.0 Crash Report [@ shutdownhang | NtQueryAttributesFile ] is the crash signature for the one crash report you furnished. Do you get this same crash often?

You have privacy.sanitize.sanitizeOnShutdown set to "true" in your list of Important Modified Preferences which you posted at http://postimg.org/image/rkr0li9bd/ This means you have selected the option to Clear history when Firefox closes in your Privacy Options, under "Use custom settings for history". Does it stop the "shutdownhang" crash if you uncheck that option?. See Settings for privacy, browsing history and do-not-track for details.

P.S. These "shutdownhang" crashes are new in Firefox 36, which is mentioned in the Firefox 36.0 Release Notes:

Changed |Shut down hangs will now show the crash reporter before exiting the program.

So, if UNchecking the box to "Clear history when Firefox closes" in your Firefox Privacy Options doesn't help (that option ued to cause a hang in earlier Firefox versions) then try basic troubleshooting to find out why Firefox isn't closing properly. I would start here: Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems.

I have to wait more time, since this crash happens after a lot of hours usage, at FF shutdown, after clicking X for closing ff.

No. History is NOT cleared. Only once a month, done manually. I need the History. I have (since years) selected "Delete cache & coockie when closing ff" (I never had issues at this point).

hmmm noscript wot, adb are not causing the hang. maybe H/W acceleration (activated here since a lot of years). its strange that with ff36 my gpu were unable to guarantee H/W acceleration (while it do well with 4k videos!), I can try disablig it, but this were NOT a solution. and its strange that nvidia, intel, amd are unable to guarantee hw accel with ff36...and zero minidump. My card is not so old (gtx650). In any case Ihave to wait more hours usage before closing ff.

anuswara said

I have (since years) selected "Delete cache & coockie when closing ff"

Maybe so, but try turning off the option to clear your history (cache and cookies, whatever) when Firefox closes temporarily to see if it helps. If you really don't want to try that then you could start here:

• Troubleshoot extensions, themes and hardware acceleration issues to solve common Firefox problems

yes, I try UNchecking the box, thanks.

Let all cookies expire when Firefox is closed to make them session cookies.

• Firefox/Tools > Options > Privacy > "Use custom settings for history" > Cookies: Keep until: "I close Firefox"

Create a cookie 'allow' exception for cookies that you would like to keep.

• Firefox/Tools > Options > Privacy > "Use custom settings for history" > Cookies: Exceptions

If you clear cookies when you close Firefox then Firefox will also try to remove cookies (local objects) from plugins like Flash and this can cause problems.

1) @cor-el Since years I have exactly this setting Keep until: "I close Firefox" ! + excepitions for google & FB to avoid the annoying re-login. and flash player does not store cookies on my pc, I verified the settings and " 0KB" stored (therefore for each video TY , every time in the same session, I have to re-set manually the volume level, due to "NO flash cookie". good so ;)

Additionally I use to set Clear cache &coockies at ff shutdown (but I remain logged into mozilla, YT, FB !! so I guess that Keep until: "I close Firefox" overriedes the box Clear cache &coockies.

2) Anyway I just closed FF after setting https://support.mozilla.org/it/questions/1050362#answer-699336

and all went fine. Now I check again the box (i.e. my normal and wanted behaviour) and tomorrow at night I will see if this "new" kind of crash (I dont see any related bug in bugzilla) is still here.

[ Now I upgrade to 36.0.1 oh I see a lot of changes in the changelog, regarding crash too....we will see what happens ;) ]

At the moment I can establish that History, coockie storage, acceleration do no matter with my crash. yesterday and today: no crash. Its strange that we can not obtain more infos reading the crash report, this would help much more than troubleshooting page. perhpas in the future a more exhaustive report may be implemented? because for normal user its not easy to perform all the tasks in troubleshooting page (other than the time it requires...)

So, you are no longer experiencing crashes at shutdown, whether or not you change your settings or keep them as-is?

Was it only the one crash, https://crash-stats.mozilla.com/report/index/b60e27a7-4e61-4158-b40d-08d6b2150304 or did you have more than one crash since your Firefox 36.0 update? Maybe Firefox 36.0.1 fixed the problem?

In any case, please post back if you get another crash and post the crash Report ID or a link to the report.

yes, maybe 36.0.1 fixed the problem. the latest changelog refers to crash too. https://crash-stats.mozilla.com/report/list?product=Firefox&signature=shutdownhang+|+NtQueryAttributesFile the percentage of the number of the crashes did not increase, good thing. ok if I experiece other crashes I post here the ID (now I deleted the crash folder). I warmly thank you.

If clearing data automatically at shutdown causes crashes, what about clearing from the History menu manually? I took to doing that with Firefox because there are times when I do not want data removed on shutdown. It seems to me that Firefox 36 has a lot of new problems.

warning: again the crash at FF shutdown. https://crash-stats.mozilla.com/report/index/05761a44-3929-4a66-b836-e90412150310

ID bp-05761a44-3929-4a66-b836-e90412150310

7th march: zero crash 8th march: zero today: crash after closing ff!

what I did? what I changed today?? nothing!

as you see skunk_classifier: reject - not a plugin hang

help please. is the crash report useful for indentifying the problem?

despite this red highlighted https://crash-stats.mozilla.com/report/index/05761a44-3929-4a66-b836-e90412150310 Nvidia says Its not due to the gpu drivers.

something to do with this old (fixed) crash? https://bugzilla.mozilla.org/show_bug.cgi?id=1008759

even if (not?) related: mozilla should to publish the minimum system requirements for H/W acceleration enabled: for example: "for H/W working in FF the minimum Nvidia driver is 344.41.....for AMD is 123.12...." mozilla should be very clear regarding the drivers. it is nonsense that "old" driver october 2014 is working well with H/W acceleration for 4K videos (!!) but issues with a browser. really does FF need more powerfull driver than 4K videos from camcorder? for doing what?

The new crash Report ID bp-05761a44-3929-4a66-b836-e90412150310 has this signature: Firefox 36.0.1 Crash Report [@ shutdownhang | RtlFreeHeap | HeapFree | nvwgf2um.dll@0x7ae300 ] The report also has no related bug reports listed.

The fixed bug you found (Bug 1008759 - [e10s] + Optimus (NVidia) crash in [ nvwgf2um.dll@0x134a04 ] ...) also refers to the NVidia file nvwgf2um.dll shown in your shutdownhang crash report but as you mentioned, it's a fixed bug.

Did you get the new shutdownhang crash with Hardware Acceleration disabled in your Firefox Options (Advanced panel General tab)?

I'll escalate this question to the Mozilla Helpdesk. It can take 72 hours for a reply.

In the meantime, you (or anyone else reading this thread) could look through this list of current Firefox 36 shutdownhang crashes and check the other filed bug reports for anything helpful.

You could create a new Firefox profile and use it for testing purposes, to see if you still experience "shutdownhang" crashes. See Profile Manager - Create, remove or switch Firefox profiles.

yes I have H/W acceleration active (since years, and since my card does support the acceleration). thanks for posting the links and for escaling to helpdesk. In the meantime I file a "bug" on custhelp nvidia, to understand deeper the driver issue (?).

its a bit strange: the latest driver is 345, while the previous is 347!!

Alice I installed 347.52 suggested by nvidia. we will see what happens ;)

Its unfortunate that this is affecting the performance of Firefox, until the issue is addressed disabling hardware acceleration is the work around that I can offer.

Please do post back about the outcome of changing drivers.

the issue is definitively NOT dued to nvidia drivers. i.e. very good with older driver, very good with the latest. In my opinion the issue is dued to the relationship FF and flash. Mozilla started too late to collaborate with Adobe, 2 years later. I rememberbugzilla for years "its due to adobe, its due to adobe..." and now I read that Mozilla is working on another kind of sandbox for ....flash. in the meantime mine friends switched to google chrome (and flash sandbox for firefox was not released in january 2015, a some years before  ;)

please read my last answer here https://support.mozilla.org/it/questions/1046755?page=2#answer-703020

yes in the last months a spend more time to write here and for troubleshooting than for web browsing.

my friend do you know what is the main problem, a bigger problem than hangs and crash?

the big problem is that firefox crash report is simply unuseful (sometimes misleading? see my post about nvidia driver) and bugzilla can only say "not reproducible" . you can see that the main bugzilla page for flash hangs is still open, after...2012. 2012-2015-.....2029? In my opinin Mozilla spent too time for interface "amelioraments" (bar up bar botton, icon smaller icon bigger australis hello, social social social, again social networking and not enough time spent for sandbox, acceleration, ram usage...in my opinion). I remember a post of a Mozilla (not US-) moderator like "I am asking to myself if Mozilla devs use Firefox or Chrome?" only when a firefox crash report will really help the dev to understand the issue, we have the real solution, otherwise we can try the next 5 years trying this one trying this other (and in the meantime I become old ;) or saying not reproducible. summary: nvidia driver: not related with all my topic on this forum.

PS: to resolve a blue screen at FF shutdown I had to purchase a new headphones set. you will tell "the USB audio driver was corrupt" wrong! only for FF it was corrupt, not for any other applications (FF changed something, not my driver went corrupted), in this case I resolved the bluescreen at FF shutdown (but never bluescreen with IE9, VLC, MPC-HC which used the same usb audio driver as FF) with...money! ;)

(I also posted this in your other support thread, /questions/1046755)

I just came across this thread in the mozilla.support.firefox newsgroup and thought you might want to read through it so see if anything is helpful: FF Locks up with Flash (The problem in this case was a conflict with Malwarebytes Anti-EXPLOIT software and the solution was to disable the software)

Thanks Alice for your reply, much appreciated. and thanks for your patience!

I guess that the user Fred S*** has OS problem too, since he wrote "I have been also dealing with another type of hang using my Laptop which causes a major slowdown when using windows explorer. Just clicking on a file to rename it or to copy or move, sometimes results in the dreaded pulsing activity circle going on and on" also not only flash hang. One day without hangs is not enough, we should wait at least one week without hangs ;)

Regarding my crash above i.e. https://crash-stats.mozilla.com/report/index/fdf2d6c9-a8ac-4f61-a82c-ad8242150312 Campbell (Adobe) told me that it is "fast" sure that flash 17.0.0.134 resolved this crash! Good. Yesterday and today I dont experience this crash. Regarding the other flash hang (https://bugzilla.mozilla.org/show_bug.cgi?id=789379), I wait if Campbell reply to me this evening too, as it happened yesterday. At the moment I dont have this hang. But I wait one (oe two) week before to say "resolved". I dont have toolbars, which may cause issues. If I have more news from Chris or other reports I write here. It is important to say that all my problems NEVER happened watching YT videos with flash, but doing other tasks while watching: e.g. switch between tabs, open a link in new tab, or just after upgrading flash (adobe splash screen with "you have the latest version" ... therefore its better offline installer than online, I agree with people in the link you posted. example: after installing flash plugin FF opens to display "you have the latest plugin version...", then I installed flash for IE, FF opens in a new window "you have the latest version activex...at this point : hang)). Summary: the crash should be fixed with flash 17, the hangs ("without steps to reproduce") occurs only when doing **other tasks in FF** while watching, yesterday and today ok. thanks again :)