X
Tap here to go to the mobile version of the site.

Support Forum

This thread was archived. Please ask a new question if you need help.

printing after 3.6.6 update results in unresponsive script

AnonymousUser
AnonymousUser
Posted

chrome://global/content/printUtils.js:48 after 3.6.6 update printing hangs with unresponsive script: chrome://global/content/printUtils.js:48.

how to I back up to 3.6.5 until this is fixed?

Crash ID(s)

chrome://global/content/printUtils.js:48

chrome://global/content/printUtils.js:48 after 3.6.6 update printing hangs with unresponsive script: chrome://global/content/printUtils.js:48. how to I back up to 3.6.5 until this is fixed? == Crash ID(s) == chrome://global/content/printUtils.js:48
  • Question details
    Product Firefox
    System Details
    • Mac OS X 10.4
    • Firefox 3.6.6

Additional System Details

Installed Plug-ins

  • -Runs Java applets using the latest installed versions of Java. For more information: Java Embedding Plugin. Run version test: Java Information.
  • Gecko default plugin
  • WebEx General Plugin Container Version 166
  • Java 1.3.1 Plug-in
  • RealPlayer Plugin
  • Adobe Acrobat and Reader Plug-in for Web Browsers, Version 7.0.9
  • The Flip4Mac WMV Plugin allows you to view Windows Media content using QuickTime.
  • 1.0.30715
  • Shockwave Flash 10.0 r32
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in web pages. For more information, visit the QuickTime Web site.

Application

  • User Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.2.6) Gecko/20100625 Firefox/3.6.6

More Information

chrome://global/content/printUtils.js:48

Close
AnonymousUser
AnonymousUser
Posted

Question owner

All the 3.6 versions after 3.6.3 have the same problem. Not sure if 3.6.3 introduced it. I've downgraded to 3.5.10 to get rid of it on most computers, hope they resolve it before August when they drop support for 3.5!!!

All the 3.6 versions after 3.6.3 have the same problem. Not sure if 3.6.3 introduced it. I've downgraded to 3.5.10 to get rid of it on most computers, hope they resolve it before August when they drop support for 3.5!!!
AnonymousUser
AnonymousUser
Posted

Question owner

I upgraded and the same thing is happening to me.

I upgraded and the same thing is happening to me.
AnonymousUser
AnonymousUser
Posted

Question owner

Save to PDF in print menu on Mac OS X Snow Leopard causes this error: chrome://global/content/printUtils.js:48 pdf - no pdf is created or saved.

Save to PDF in print menu on Mac OS X Snow Leopard causes this error: chrome://global/content/printUtils.js:48 pdf - no pdf is created or saved.
AnonymousUser
AnonymousUser
Posted

Question owner

Meu sistema é windows vista starter e estou tendo o mesmo erro de script.

Quando peço para imprimir alguma pagina, demora muito tempo e aparece a mensagem:

"UM script desta pagina pode estar em execuçao ou parado de responder. Você pode interrompê-lo agora ou continuar para verificar se ele termina a execuçao.

chrome://global/content/printUtils.js:48"

Nao entendi muito bem como posso solucionar o problema... tenho que voltar a uma versao anterior do firefox?????

Meu sistema é windows vista starter e estou tendo o mesmo erro de script. Quando peço para imprimir alguma pagina, demora muito tempo e aparece a mensagem: "UM script desta pagina pode estar em execuçao ou parado de responder. Você pode interrompê-lo agora ou continuar para verificar se ele termina a execuçao. chrome://global/content/printUtils.js:48" Nao entendi muito bem como posso solucionar o problema... tenho que voltar a uma versao anterior do firefox?????
AnonymousUser
AnonymousUser
Posted

Question owner

What is causing these "unresponsive script" errors?

What is causing these "unresponsive script" errors?
the-edmeister
the-edmeister
  • Top 25 Contributor
  • Moderator
5068 solutions 37363 answers
Posted

colin,

That is caused by an extension called something like Search Shield, which I believe is an AVG extension. Disable it until an updated version is available.

colin, That is caused by an extension called something like Search Shield, which I believe is an AVG extension. Disable it until an updated version is available.