Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

Dette websted vil have begrænset funktionalitet, mens vi gennemgår vedligeholdelse for at forbedre din oplevelse. Hvis en artikel ikke løser dit problem, og du vil stille et spørgsmål, har vi vores supportfællesskab, der venter på at hjælpe dig på @FirefoxSupport på Twitter og/r/firefox på Reddit.

Avatar for Username

Søg i Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Læs mere

Denne tråd blev arkiveret. Stil et nyt spørgsmål, hvis du har brug for hjælp.

script stopped or not responding modules/XPCOMUtils.jsm:328 happens consistantly when opening gmail. What can I do to fix or workaround?

  • 1 svar
  • 293 har dette problem
  • 6 visninger
  • Seneste svar af DarrenShultz

ewcbhc
ewcbhc
more options

Mozilla Firefox V3.6.12 DSL att uverse 3mb/sec The message may take 30 seconds to several minutes before it will display. The mouse and keyboard are unable to affect the browser while waiting. CPU is idle. The cursor will move,but the keyboard and mouse buttons have no affect. After the message is displayed and the script is stopped. Everything returns to normal. The wait time is very exasperating. Any help would be greatly appreciated. Windows XP is SP3 + .

Mozilla Firefox V3.6.12 DSL att uverse 3mb/sec The message may take 30 seconds to several minutes before it will display. The mouse and keyboard are unable to affect the browser while waiting. CPU is idle. The cursor will move,but the keyboard and mouse buttons have no affect. After the message is displayed and the script is stopped. Everything returns to normal. The wait time is very exasperating. Any help would be greatly appreciated. Windows XP is SP3 + .

Alle svar (1)

DarrenShultz
DarrenShultz
more options

Had this issue on Mac OS, ran disk utility and repair permissions. Solved the problem. Not sure if the cause/solution is similar for Windows XP.