Fungovanie tejto stránky je z dôvodu údržby dočasne obmedzené. Ak článok nevyrieši váš problém a chcete položiť otázku, napíšte našej komunite podpory na Twitter @FirefoxSupport alebo Reddit /r/firefox.

Vyhľadajte odpoveď

Vyhnite sa podvodom s podporou. Nikdy vás nebudeme žiadať, aby ste zavolali alebo poslali SMS na telefónne číslo alebo zdieľali osobné informácie. Nahláste prosím podozrivú aktivitu použitím voľby “Nahlásiť zneužitie”.

Ďalšie informácie

SOLVED: A script error (gtm.js?id=GTM-WVZNLW) is fouling printing and crashing Firefox

  • 9 odpovedí
  • 1 má tento problém
  • 1 zobrazenie
  • Posledná odpoveď od Jeff Grossman

more options

When I try to print to my LAN-attached-by-ethernet Canon MF8350Cdn printer, a script error windows flashes on|off, the print job never makes it to the printer, Firefox closes and displays a Crash Report window. My work-around is printing to a PDF.

When I print to a PDF using PrimoPDF, a script error windows displays and waits for Y|N input, on clicking Yes, I am able to print to a PDF successfully. I can then print from Adobe Reader or Acrobat Standard to the same Canon printer successfully. That's as good as it gets.

Going to about:crashes reveals a couple of memory management issues, specifically in cnxdias2.dll (Canon printer file) and dpofeedb.dll (DigitalPersona Pro loaded by dpagent.exe?). I have diligently sent in the crash reports but have no clue what happens afterward.

Attached is a screen shot of the error.

When I try to print to my LAN-attached-by-ethernet Canon MF8350Cdn printer, a script error windows flashes on|off, the print job never makes it to the printer, Firefox closes and displays a Crash Report window. My work-around is printing to a PDF. When I print to a PDF using PrimoPDF, a script error windows displays and waits for Y|N input, on clicking Yes, I am able to print to a PDF successfully. I can then print from Adobe Reader or Acrobat Standard to the same Canon printer successfully. That's as good as it gets. Going to about:crashes reveals a couple of memory management issues, specifically in cnxdias2.dll (Canon printer file) and dpofeedb.dll (DigitalPersona Pro loaded by dpagent.exe?). I have diligently sent in the crash reports but have no clue what happens afterward. Attached is a screen shot of the error.
Priložené obrázky

Upravil(a) Sky dňa

Vybrané riešenie

Jeff Grossman said

I see malware scans on the 'net with the exact same gtm tag which means other people are having the same problem as you. On one Nitro board the admin said to do a 'repair' on PrimoPDF. Worth a try.

Yes it was!

This advice led me to look at PrimoPDF as the originating culprit for the googletag JavaScript error. PrimoPDF has been owned, and now essentially orphaned, by Nitro PDF for some years now. The latest version July 26, 2010 when Nitro incorporated their advertising box on the opening page.

I dl'd another copy of PrimoPDF just in case my installation copy was bad. The only type available is 32-bit, although a 64-bit version exists... somewhere. Next was uninstall-reinstall, then check. On launching my newly-installed version of the very same program I found different settings caused odd behavior, from my notes:

Screen displays OK eBook 502 Bad Gateway (cloudfare) error Print script error https://www.googletagmanager.com/gtm.js?id=GTM-WVZNLW Prepress script error https://www.googletagmanager.com/gtm.js?id=GTM-WVZNLW Custom (default) script error https://www.googletagmanager.com


After hitting Custom, all now show the script error. Trying variations made no difference. UN- RE-INSTALL, launch - same issues as after Custom. Options > stop Streamlining. Reopen, started OK, showed Custom settings although all are default except streamlining.

PrimoPDF appears to have been the source of the JavaScript error, and in Primo the "streamlining" option appears to be the root cause. That it happened coming off of Firefox appears to have been happenstance.

Now the only thing that flashes on the screen looks like an error — but it is not. It's a very fast Print Preview | Progress flag saying the preview is preparing. I was able to capture and see it using the Microsoft Steps Recorder in Windows 10.

Thanks, Jeff!


EDIT For anyone interested, it's worth noting PrimoPDF is (now officially) a discontinued product seen today on Nitro PDF's web site here no wonder they haven't updated it—but they still have it for download. — Sky

Čítať túto odpoveď v kontexte 👍 0

Všetky odpovede (9)

more options

this happens for all print jobs regardless of the source?

more options

Eve said

this happens for all print jobs regardless of the source?

Yes... for all print jobs from Firefox, regardless of web site/form such as web page or pdf being viewed. Any print job originating from Firefox.

Upravil(a) Sky dňa

more options

so print jobs originating from other programs or browsers work fine? I'm asking around

more options

Sort of... it's very hit-and-miss

  • Notepad crashes, displays 'stopped working' window & closes;
  • QuickBooks, a notorious problem child, usually prints OK;
  • Adobe Reader/Acrobat print OK;
  • Microsoft Edge 44.18362.449.0 | EdgeHTML 18.18363 prints OK (but it breaks web sites);
  • Chrome v80.0.3987.149 x64 dies similarly to Firefox but without the dialogue box or error report box — just crash & close (and breaks web sites); and
  • Internet Explorer 11.719.18362.0 crashes & restarts (but doesn't break web sites — they just refuse to work under IE and tell you to update or go away)

The work-around of printing to a pdf first, then printing the pdf as hardcopy is pretty reliable except for this googletag issue popping a js error.

more options

Perhaps your printer driver is messed up in some way? Can you make sure that's updated? Or maybe it updated recently and it broke it?

more options

The printer driver is up-to-date and not broken. It's been un- and re-installed with no change. If it's the printer driver I wouldn't expect it to print at all... plus, this really is the wrong place for me to pursue issues with the printer driver.

The GoogleTag JavaScript issue that's plaguing me is what I'm chiefly concerned with fixing at this point. Do you envision some way an errant print driver could cause a JavaScript googletag issue?

EDIT AFTER SOLVED PrimoPDF is also a printer driver. I was only considering the Canon driver. This was definately the right path as shown below—Sky

Upravil(a) Sky dňa

more options

Hi Sky,

I see malware scans on the 'net with the exact same gtm tag which means other people are having the same problem as you. On one Nitro board the admin said to do a 'repair' on PrimoPDF. Worth a try.

Good luck.


Jeff

more options

Vybrané riešenie

Jeff Grossman said

I see malware scans on the 'net with the exact same gtm tag which means other people are having the same problem as you. On one Nitro board the admin said to do a 'repair' on PrimoPDF. Worth a try.

Yes it was!

This advice led me to look at PrimoPDF as the originating culprit for the googletag JavaScript error. PrimoPDF has been owned, and now essentially orphaned, by Nitro PDF for some years now. The latest version July 26, 2010 when Nitro incorporated their advertising box on the opening page.

I dl'd another copy of PrimoPDF just in case my installation copy was bad. The only type available is 32-bit, although a 64-bit version exists... somewhere. Next was uninstall-reinstall, then check. On launching my newly-installed version of the very same program I found different settings caused odd behavior, from my notes:

Screen displays OK eBook 502 Bad Gateway (cloudfare) error Print script error https://www.googletagmanager.com/gtm.js?id=GTM-WVZNLW Prepress script error https://www.googletagmanager.com/gtm.js?id=GTM-WVZNLW Custom (default) script error https://www.googletagmanager.com


After hitting Custom, all now show the script error. Trying variations made no difference. UN- RE-INSTALL, launch - same issues as after Custom. Options > stop Streamlining. Reopen, started OK, showed Custom settings although all are default except streamlining.

PrimoPDF appears to have been the source of the JavaScript error, and in Primo the "streamlining" option appears to be the root cause. That it happened coming off of Firefox appears to have been happenstance.

Now the only thing that flashes on the screen looks like an error — but it is not. It's a very fast Print Preview | Progress flag saying the preview is preparing. I was able to capture and see it using the Microsoft Steps Recorder in Windows 10.

Thanks, Jeff!


EDIT For anyone interested, it's worth noting PrimoPDF is (now officially) a discontinued product seen today on Nitro PDF's web site here no wonder they haven't updated it—but they still have it for download. — Sky

Upravil(a) Sky dňa

more options

You're welcome, Sky.