1415347 - Cancelling print request to doPDF corrupts SeaMonkey and blocks further printing

Status: RESOLVED WONTFIX

(SeaMonkey :: General, defect, P3)

Description

[David E. Ross]

Attachment: Error popup when attempting to print after cancelling a print-to-PDF.

Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 SeaMonkey/2.49.1

I have the print-to-PDF application doPDF 9.0.217 installed.  To print-capable applications, this appears to be another printer.  However, it results in a PDF file being generated instead of actually printing to paper.  

If I start to print a Web page to a PDF file via doPDF and then cancel the operation, I can no longer print from SeaMonkey even to my default print (an HP LaserJet Pro 200 Color).  Instead, I get an error popup.  If I then try to open another Web page via SeaMonkey, I get a different error popup.

Comment 1

[David E. Ross]

Attachment: Error popup when I try to visit a Web page after cancelling a print-to-PDF.

Comment 2

[David E. Ross]

If it is not clear in my original Description, the problem occurs when I cancel a print-to-PDF request that has not yet completed.  

I get the same error operating in Safe Mode.  I find the only way to restore SeaMonkey's operations is to terminate it and then relaunch it.  Since SeaMonkey uses Mozilla's Core and Toolkit components, I strongly suspect this is also a Firefox problem.  

Note that I do not have a similar problem after cancelling an incomplete print-to-PDF request in Word, which is why I do not think this is a doPDF problem.  In any case, I am not attempting to print when I get the error popup shown in Attachment 8926134 [details]; thus, doPDF should not be involved with that.

Comment 3

[Mantaroh Yoshinaga[:mantaroh]]

(In reply to David E. Ross from comment #2)
> If it is not clear in my original Description, the problem occurs when I
> cancel a print-to-PDF request that has not yet completed.  
> 
> I get the same error operating in Safe Mode.  I find the only way to restore
> SeaMonkey's operations is to terminate it and then relaunch it.  Since
> SeaMonkey uses Mozilla's Core and Toolkit components, I strongly suspect
> this is also a Firefox problem.  
> 
> Note that I do not have a similar problem after cancelling an incomplete
> print-to-PDF request in Word, which is why I do not think this is a doPDF
> problem.  In any case, I am not attempting to print when I get the error
> popup shown in Attachment 8926134 [details]; thus, doPDF should not be
> involved with that.

Thanks for reporting.

Yes, Cancelling problem is same of bug 1409971. This cause is that gecko doesn't set cancelling flag on multi process environment.

I set duplicate flag, but feel free to reopen if you have other problem.

Comment 4

[David E. Ross]

Bug #1409971 is about the inability to cancel a print request.  In my case, I was indeed able to cancel the print-to-PDF request.  Only after that did my browser go crazy.  Furthermore, I am able to cancel other print requests (e.g., print-to-fax) without any problem.

Comment 5

[David E. Ross]

doPDF is NOT an add-on.  It is not listed as an add-on by the Add-ons Manager.  It is effectively a printer just as are my HP LaserJet 200 color M251 PCL 6 and the Windows Fax application (WFS.exe).

Comment 6

[Jonathan Watt [:jwatt]]

Thanks for fixing and clarifying, David.

I have a partial patch for bug 499025 that I need to finish off that fixes some of the printing error handling brokenness. It will be worth rechecking this bug after the fix for that one lands.

Comment 7

[David E. Ross]

I only use SeaMonkey, and I will upgrade to a newer version of SeaMonkey only as long as it still supports .xpi extensions.  If the next version does support .xpi extensions, I will test to see if this bug report can be closed.

Comment 8

[Jonathan Watt [:jwatt]]

Is this still an issue for you, David?

Comment 9

[David E. Ross]

I am still using SeaMonkey 2.49.5 (old) under Windows 7 (older) with doPDF 11.3.248 (latest). Yes, this is a problem for me. For Web sites that block that version of SeaMonkey, I use Firefox 92.0.2, which does NOT have this problem.

Comment 10

[Jonathan Watt [:jwatt]]

Thanks, David. That's a shame. :-( Unfortunately the chances of us figuring out and fixing this issue for a five year old version of SeaMonkey are pretty much zero, to be honest. I'll close this bug to reflect reality.