https://crash-stats.mozilla.com/report/index/54db8783-53c5-4a42-b1b1-a71c12150323 again

129 peoples read this topic, but....solution please?

anuswara said

https://crash-stats.mozilla.com/report/index/54db8783-53c5-4a42-b1b1-a71c12150323 again 129 peoples read this topic, but....solution please?

There are no related bugs listed for that crash Report ID bp-54db8783-53c5-4a42-b1b1-a71c12150323 Firefox 36.0.4 Crash Report [@ shutdownhang | RtlFreeHeap | HeapFree | nvwgf2um.dll@0x7f4970 ]

You can help yourself and others get to the bottom of these "shutdownhang" crashes if you file your own bug report, using one of the "Report this bug" links in the crash report Related bugs section.

Have you tried turning off hardware acceleration in the Firefox Advanced panel General tab? That's what the Helpdesk person guigs2 suggested here in /questions/1050362#answer-702981 as the workaround, if changing graphics drivers doesn't help.

since it still happens, with the latest driver too, and since I am wondering if FF36 would not support H/W acvceleration, I filed a bug on bugzilla. we will see...

@anuswara Just to follow up, was there improvements seen in the current 37 release? The graphics cards that have been blocked do not have yours listed:

• https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers#NVIDIA_card...

It crashes right clicking all the Vatican videos from vatican.va. (silverlight, NEVER had problem with silverlight since years). Bugzilla did not reply to my bug (perhaps they are busy with crash at startup fixed in upcoming 37.0.1 : I do not experience those crash).

Nvidia, depite mozilla creash report that you see above, told me that its NOT due to nvidia driver. Since video driver are *always* involved (even watching an email), even in this case they may be not the real cause of the shutdownhang.

Improvement: better horizontal scrolling, better ram usage in Facebook photo albums (scrolling very long albums).

Now Nvidia is invetigating the new feautures of ff37, regarding the rendering (D3D9> D11).

At the moment No crash with: nvwgf2um.dll@0x7f4970 but since nvidia (and bugizlla!) did nothing regarding this issue, I prefer to wait at least one week to see if this kind of crash occurs again.

thank for posting the list, much appreciated. it seems a bit old right?

PS. perhaps vatican.va videos have issue, since other people told me that they are unable to switch in full screen mode (no botton available), instead all is ok with silverlight on rai.it videos.

Yes, and looking at it again it has not been updated, sorry about that.

nvwgf2um.dll@0x7f4970

The issue was due to Firefox, not to Nvidia driver, despite the crash report (wrong crash report generated by firefox?), since with FF37 - and with the same driver - I dont experience this hang at shutdown.

Again! https://crash-stats.mozilla.com/report/index/3f1ab399-2480-4be9-bc8f-4e2282150414

there is a way to get ram in rom, not written on hard disk, as in the past versions?

anyway: https://bugzilla.mozilla.org/show_bug.cgi?id=1154353 we will se if there will be a way to resolve this annoying behaviour.

unconfirmed > NEW.

https://crash-stats.mozilla.com/report/index/44252764-a492-4a3b-8b59-ae8962150420

NEW...and sleeping ;)

Even if it is unuseful, I filed a new bug https://crash-stats.mozilla.com/report/index/a1fb0e68-3f39-42b3-8972-bd5b52150425#details

because FF crashes a bit too often, while in the past once at year only. https://bugzilla.mozilla.org/show_bug.cgi?id=1158482 even if the file is big in size, ff should be able to save it on desktop.

Hi Alice,

1)

all my problems (*despite* all the crash reports!! hehehe) has been **fully resolved** (this questions/1046755 too) how? ....by simply switching from NIS Norton to CIS Comodo 8.2  !!!!

2)

not good that HTML5 does NOT support HW acceleration. Youtube: with flash = CPU 8% with html5 (default in Firefox! wonderful buffering compared to flash where the buffer go lost) = CPU 33% not good that after 12 years studies and efforts we have NO GPU via html5.

3)

perhaps OT, sorry Alice, but **very very important** for you and developers:

the latest nvidia driver with works fine on FF (obviously HW acceleration ON !!!) is

347.88

(regardless the cards, i.e. from GTX500 until GTX980 !!)

all newer drivers generate a "nvlddmkm stopped working and has been recovered", in both FF and Chrome.

https://forums.geforce.com/default/topic/836914/geforce-drivers/official-nvidia-353-06-whql-game-ready-display-driver-feedback-thread-released-5-31-15-/1/

the "Nvidia 2-level support" will re-contact me. Please send this post to other mozilla dev.

until 347.88 al is fine. then....a catastrophe.

thanks. regards,