875691 - FireFox 29.0 Still Does Not Work Correctly with the Adobe Acrobat 10.1.9 PDF Printer Driver

Status: RESOLVED WORKSFORME

(Core :: Printing: Output, defect)

Description

[Cypherdude]

FireFox used to work correctly with the Adobe 10.x Printer Driver.  However, after upgrading to v21.0, I am constantly getting the AppHangXProcB1 error.  I have not been able to reliably reproduce this error.

It COULD have something to do with when I change folders in the "Save PDF File As" window.  NOT changing folders and NOT entering a file name, leaving the name as is, and immediately saving it seems to avoid the AppHangXProcB1 error.

Here is the text of the Windows crash:
============================================
Description:
  A problem caused this program to stop interacting with Windows.

Problem signature:
  Problem Event Name:	AppHangXProcB1
  Application Name:	firefox.exe
  Application Version:	21.0.0.4879
  Application Timestamp:	518ec3cc
  Hang Signature:	59cd
  Hang Type:	128
  Waiting on Application Name:	splwow64.exe
  Waiting on Application Version:	0.0.0.0
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033
  Additional Hang Signature 1:	59cd08287e5c10bb7f3d91bc38d8b3da
  Additional Hang Signature 2:	6ae9
  Additional Hang Signature 3:	6ae9c5d10979e2b960ee0773dce8bce7
  Additional Hang Signature 4:	59cd
  Additional Hang Signature 5:	59cd08287e5c10bb7f3d91bc38d8b3da
  Additional Hang Signature 6:	6ae9
  Additional Hang Signature 7:	6ae9c5d10979e2b960ee0773dce8bce7

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Comment 1

[Cypherdude]

Attachment: FireFox 21.0 has frozen when trying print to PDF using Adobe v10.1.7 Printer Driver, with notes.

This is the "Save PDF File As" window.  As you can see, it is "Not Responding".  Sometimes just trying to change the folder on the top space/row can cause FireFox 21.0 to freeze.  I first noticed this behavior with FF 21.0 after I upgraded from FF 17.x.

There are notes in this screenshot.  Look for the large red arrow.

Comment 2

[Cypherdude]

Attachment: FireFox 21.0 AppHangXProcB1's and causes Adobe PDF spool to be stuck.

After FireFox 21.0.0.4879 AppHangXProcB1's, it causes the print job to stay stuck in the print spool for the Adobe PDF printer driver.  After FF 21.0 AppHangXProcB1's, I cannot remove the print job from the driver's print spool.  This AppHangXProcB1 behavior is new to FF 21.0.  This did not happen before.

Comment 3

[Cypherdude]

Attachment: FireFox 21.0 stuck in RAM even after I choose to "Close the program."

After FireFox 21.0.0.4879 AppHangXProcB1's, even after I close FF part of it gets stuck in RAM.  The only way to completely remove FF 21.0 is to use Windows 7-64 Task Manager and End Process.  After FF 21.0 AppHangXProcB1's, it causes my entire system to become unpredictable because it also interferes with other applications.  It causes other applications to behave strangely.  I suspect the hanged FF 21.0 also ties up RAM which should be freed.

Comment 4

[Cypherdude]

Attachment: FireFox 21.0 AppHangXProcB1's yet again and causes Adobe PDF spool to be stuck.

Here we have FireFox 21.0 giving off yet another AppHangXProcB1 which causes the Adobe PDF print job to be stuck.

Comment 5

[Cypherdude]

Description:
  A problem caused this program to stop interacting with Windows.

Problem signature:
  Problem Event Name:	AppHangXProcB1
  Application Name:	firefox.exe
  Application Version:	21.0.0.4879
  Application Timestamp:	518ec3cc
  Hang Signature:	59cd
  Hang Type:	128
  Waiting on Application Name:	splwow64.exe
  Waiting on Application Version:	0.0.0.0
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033
  Additional Hang Signature 1:	59cd08287e5c10bb7f3d91bc38d8b3da
  Additional Hang Signature 2:	6ae9
  Additional Hang Signature 3:	6ae9c5d10979e2b960ee0773dce8bce7
  Additional Hang Signature 4:	59cd
  Additional Hang Signature 5:	59cd08287e5c10bb7f3d91bc38d8b3da
  Additional Hang Signature 6:	6ae9
  Additional Hang Signature 7:	6ae9c5d10979e2b960ee0773dce8bce7

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Comment 6

[Cypherdude]

Attachment: FireFox 21.0 AppHangXProcB1's again and causes another Adobe PDF spool to be stuck.

Comment 7

[Edoardo Tirtarahardja]

I also experience exact same issue with FireFox 23.0.1 and Adobe PDF Driver 10.1.7.3 on my Win7 64 bit Enterprise. Occurs intermittently several times. The doc. seems to be stuck in Adobe PDF printer spool.

Comment 8

[Cypherdude]

I currently have FireFox 23.0.1.  I have not yet upgraded to FF 24.0.  Adobe Pro automatically upgraded to 10.1.8.  I cannot find where the Adobe X PDF printer driver version is located.  I use the Adobe PDF printer driver to print out receipts.  I have not used FireFox to print out a PDF file in some time, probably months.

I have given up on FireFox.  I need the Adobe PDF files to obtain a receipt and also proof of payment for bills.  When I pay a bill, I cannot have FireFox crash on me.  This would give me nothing.  I now use Internet Explorer 9 whenever I pay a bill or when I need a PDF file receipt whenever I make a purchase on the 'Net.

I will wait until FF upgrades to 24.0.1.  I will then test FF and see if the Apphangs have stopped.  The problem is FireFox's Apphangs are intermittent.  They do not happen every time.  FireFox's Apphangs appear to depend on what type of content and what type of page is being printed.  Nonencrypted pages appear to print OK but I am not 100% sure.  Unfortunately, all banking and credit card pages are encrypted.  The last time I used FireFox to print to a PDF file, it AppHanged when I tried to PDF print an encrypted page.  This is why experimentation is difficult.

Comment 9

[Edoardo Tirtarahardja]

Why no body is working on this???? This is critical as we can't print to PDF. Some page, like receipt, can only be shown once and if FF hangs, then no way to print that receipt anymore. The problem is seen on EVERY FF release since FF 21 all the way to the current FF 25.0.1.

Comment 10

[Cypherdude]

Do not use FF for PDF receipts until (if) they fix it.  Use Internet Explorer.

Comment 11

[Cypherdude]

I upgraded to FireFox 28.0.  However, I am still getting AppHangXProcB1's when I try to print to PDF using the 10.1.9 Adobe Acrobat printer driver.  I was going to pay a bill and tested FF28.  However, it AppHanged on me.  I was forced to switch to IE9 which does print to PDF correctly.  IE9 has never AppHanged on me while printing to PDF.  I have been paying my bills using IE9 for about a year now.  Also, whenever I buy something online and I need a PDF receipt, I always use IE9 now.

==============================================================
Description:
  A problem caused this program to stop interacting with Windows.

Problem signature:
  Problem Event Name:	AppHangXProcB1
  Application Name:	firefox.exe
  Application Version:	28.0.0.5186
  Application Timestamp:	53240e37
  Hang Signature:	34a6
  Hang Type:	128
  Waiting on Application Name:	splwow64.exe
  Waiting on Application Version:	0.0.0.0
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033
  Additional Hang Signature 1:	34a6ebe0d8e139a357dd990ae55e5b7a
  Additional Hang Signature 2:	daa4
  Additional Hang Signature 3:	daa4e4174a9b149cf5b9d8e336a4383c
  Additional Hang Signature 4:	34a6
  Additional Hang Signature 5:	34a6ebe0d8e139a357dd990ae55e5b7a
  Additional Hang Signature 6:	daa4
  Additional Hang Signature 7:	daa4e4174a9b149cf5b9d8e336a4383c

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt
==============================================================

Comment 12

[Cypherdude]

Today, I tried to Adobe PDF print out a receipt and FireFox 29.0 AppHanged.  I lost my receipt which I need to keep records.  It looks as though Mozilla will not be fixing this bug at all.  I will no longer be making any purchases with FireFox where I need a receipt:

Description:
  A problem caused this program to stop interacting with Windows.

Problem signature:
  Problem Event Name:	AppHangXProcB1
  Application Name:	firefox.exe
  Application Version:	29.0.0.5224
  Application Timestamp:	5356318a
  Hang Signature:	d4aa
  Hang Type:	128
  Waiting on Application Name:	splwow64.exe
  Waiting on Application Version:	0.0.0.0
  OS Version:	6.1.7601.2.1.0.256.48
  Locale ID:	1033
  Additional Hang Signature 1:	d4aa1d7279305fc8bce5bb28518fa504
  Additional Hang Signature 2:	bf6f
  Additional Hang Signature 3:	bf6f2644ab8c28b0e948607a3da55f40
  Additional Hang Signature 4:	d4aa
  Additional Hang Signature 5:	d4aa1d7279305fc8bce5bb28518fa504
  Additional Hang Signature 6:	bf6f
  Additional Hang Signature 7:	bf6f2644ab8c28b0e948607a3da55f40

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt

Comment 13

[watchdogx29]

This bug has been around since 2013. I know I have been dealing with it for that long, and I am certain many, many others have as well. Yes, sometimes when you restart Firefox it works the second try, but sometimes not. I print to PDF not just as a convenience but to SAVE PAPER and thus save trees. Three years, ten major releases later this issue does not appear to have even been investigated.

PLEASE do whatever you can to raise the priority of this to at least get a look. Maybe it's an easy fix. Thank you for your consideration.

Sincerely,
- DK

Comment 14

[Cypherdude]

FireFox also AppHangs when I try to print with the Microsoft XPS Document Writer driver to file.  The bug seems to have something to do with transferring data to the print to file drivers.

I don't think any data is getting through to the the PDF and XPS drivers.  That could be why the printer spool is empty.

Comment 15

[Rares Doghi, Desktop QA]

I tried to reproduce this issue with the latest Firefox Release 89.0.2 and Acrobat Reader DC installed but without success.
Cypherdude are you still seeing this issue in our latest versions of Firefox ?

Comment 16

[Cypherdude]

I reported this problem on 2013-05-24. Although above Platform is stated as "x86_64", it was actually "x86_32" or 32 bit. I switched to Firefox 64 bit late August 2018. When I switched to 64 bit, I believe the problem went away.

I have not had any Adobe Acrobat 10.x printer driver or Microsoft XPS Document Writer driver Firefox AppHangs for some time. I can't remember the last time I've had this type of Firefox 64 bit AppHang, if ever. I don't really use the Microsoft XPS Document Writer driver. I just tested printing out this page to an XPS file using Microsoft XPS Document Writer driver and it worked fine, no problems. Slightly off topic, I don't really like Microsoft's XPS viewer or format. It seems to output to a type of picture file. You cannot highlight any text and you cannot search for text terms because the XPS search feature doesn't work.

By upgrading to Firefox 64 bit, I avoided the Firefox 32 bit AppHangs. I still have Firefox 32 bit v61.0.2 installed. However, I have not used it for years. I probably should uninstall it. I am currently using Firefox 64 bit v88.0.1. I have upgrades completely turned off using the Registry method due to the upgrade nag screens introduced in February 2019. I have not upgraded to Firefox x64 89.0.2 because I don't like the new Proton interface. I'm not sure how to proceed regarding this. I don't like the new Proton interface at all. My understanding is the About:config commands to disable Proton are only temporary.

Comment 17

[Rares Doghi, Desktop QA]

Since the main issue went away, I will close this one as a works for me, as for the latest Proton changes There are a few issues logged related to the Contrast and other Theme issues, maybe when they get fixed you will not have to stop the updates.