Closed
Bug 305406
Opened 19 years ago
Closed 16 years ago
Freeze after print to PDF Writer
Categories
(Core :: Printing: Output, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: keepitsimpleengineer, Unassigned)
References
()
Details
(Keywords: hang)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Occasionally after printing to Acrobat PDFWriter (default printer) Firefox will
crash/freeze beconing non responsive and not repainting windows, and must be
closed with Windows task manager.
Reproducible: Sometimes
Steps to Reproduce:
1.Menu-File/Print
2.OK (PDFwriter is default printer)
3.After Acrobat opens and displays printed page, return to Firefox browser.
Actual Results:
Firefox has frozen without repainting its windows. Non responsive. Must exit
browser application using Windows Task Manager. Acrobat successfully produces,
displays and saves
Expected Results:
unfrozen /responsive.
Acrobat Professional Ver 6.0.3 11-30-2004
Acrobat PDFWriter; LPT1:Printer Port; PDFWriter Driver Version 4.0 (Default Printer)
This is new behavior. I have used print to PDFWriter for months and never had
this happen.
----
about:buildconfig
Build platform
target
i586-pc-msvc
Build tools
Compiler Version Compiler flags
$(CYGWIN_WRAPPER) cl 12.00.8804 -TC -nologo -W3 -nologo -Gy -Fd$(PDBFILE)
$(CYGWIN_WRAPPER) cl 12.00.8804 -TP -nologo -W3 -nologo -Gy -Fd$(PDBFILE)
Configure arguments
--disable-ldap --disable-mailnews
--enable-extensions=cookie,xml-rpc,xmlextras,pref,transformiix,universalchardet,webservices,inspector,gnomevfs,negotiateauth
--enable-crypto --disable-composer --enable-single-profile
--disable-profilesharing --enable-optimize --disable-debug --disable-tests
--enable-static --disable-shared --enable-official-branding
Comment 1•19 years ago
|
||
Most likely a dupe of 219987
*** This bug has been marked as a duplicate of 219987 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 2•19 years ago
|
||
This is about PDF Writer, not an Adobe Reader (219987), nor actually an Acrobat
bug, since Acrobat performs correctly. It is a print bug regarding PDFWriter
and Firefox. PDF Writer is suplied as part of Acrobat. The PDFwriter version
provided with Acrobat 6 is 4.0.
I regularly open PDF documents with Firefox—and experience brief, nonresponsive
delays while reader loads bothe with Win2KPro/Reader6.0 and WinXPpro/Reader7.0,
but I have never had any on the experiences related in bug 219987.
I have been printing to PDFwriter with Firefox for months, and this has only
recently begun to occur.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Comment 3•19 years ago
|
||
(In reply to comment #2)
> I have been printing to PDFwriter with Firefox for months, and this has only
> recently begun to occur.
You mean this din't happen in FF1.0.4 and started since you upgraded to 1.0.6 ?
Reporter | ||
Comment 4•19 years ago
|
||
It starting happening in 1.05, so I upgraded to 1.06 and verified I had all
updates to Acrobat 6..., and it still happened. After it occurs and Firefox is
restarted, Firefox sems to behve normally. It is not repeatable, and I'm not
sure it's a Firefox bug.
Comment 5•19 years ago
|
||
Those are the worst kind of bugs i guess.
Another approach, disable all your extensions, in the extension manager, and see
if you still can reproduce the problem.
reporter: if you're building yourself, could you attach w/ a profiler or
debugger and get a stack trace?
Assignee: nobody → printing
Component: General → Printing
Keywords: hang
Product: Firefox → Core
QA Contact: general
Summary: Freeze/crash after print to PDF Writer → Freeze after print to PDF Writer
Version: unspecified → 1.7 Branch
Comment 7•16 years ago
|
||
several similar have been closed, and no response
=> incomplete
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 16 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•