We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Този сайт ще има ограничена функционалност, докато се извършва тече неговата поддръжка. Ако дадена статия не може реши проблема ви и искате да зададете въпрос, нашата общност е готова да ви помогне на @firefox в Twitter и /r/firefox в Reddit.

Търсене в помощните статии

Избягвайте измамите при поддръжката. Никога няма да ви помолим да се обадите или изпратите SMS на телефонен номер или да споделите лична информация. Моля, докладвайте подозрителна активност на "Докладване за злоупотреба".

Научете повече

After Firefox 7 Install D3D9 Window Not Responding At Shutdown

  • 6 отговора
  • 315 имат този проблем
  • 3 изгледи
  • Последен отговор от az99

more options

Since installing Firefox 7, every time I try to shutdown the computer, a warning opens and says D3D9 Window Not Responding. I then have to click END NOW. Windows XP SP3.

Since installing Firefox 7, every time I try to shutdown the computer, a warning opens and says D3D9 Window Not Responding. I then have to click END NOW. Windows XP SP3.

Всички отговори (6)

more options

This many people with the problem and no suggestions ?

more options

32 people with the issue and no answers ?

more options

I seemed to have minimized it by shutting down FF 7 and then waiting a minute. FF7 also crashes and locks up on restart if you shutdown the computer without going thru shut down( ie just pull plug). Maybe FF8 will be better. :)

more options
more options

Same issue with FF8 . Still no answer from FF tech support with all these people having the same issue ?

more options

Here is a portion of the above quoted link. "ONE MORE THING! The initial problem with DirectX (receiving the D3D9Window error notice on shutdown) happened immediately following my upgrading to the latest version of Firefox, Version 6.0.2. I am SURE this is not a mere coincidence, and that others upgrading their browser will probably encounter a similar problem."

So this appears to be a definite problem between FF and DirectX.

COME ON FF. GET THIS FIXED.