Crashes on attempt to print [@ nsContainerFrame::SyncFrameViewAfterReflow]

RESOLVED WORKSFORME

Status

()

Core
Printing: Output
--
critical
RESOLVED WORKSFORME
15 years ago
14 years ago

People

(Reporter: u27431, Unassigned)

Tracking

({crash, regression})

Trunk
x86
Linux
crash, regression
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature, URL)

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314

It crashes when I try to print the indicated URL.

Sorry, I get no Talkback on this (I installed from RPMs, I can see talkback in
/usr/lib/mozilla/components but can't tell if it's active).


Reproducible: Always

Steps to Reproduce:
1. Go to the indicated URL.
2. Click the "Print" icon.
3. Click then "Print" button in the dialog.

Actual Results:  
It crashes.

Expected Results:  
Printed.

System is Redhat 7.3, printing using LPRng.

Please let me know if I can assist in any way (or if you can tell me how to
determine if Talkback is running).

Comment 1

15 years ago
Created attachment 118381 [details]
stacktrace

stacktrace from print preview of URL

Comment 2

15 years ago
crash occurs with linux trunk 2003032305
this regressed between linux trunk 2002071914 and 2002072104
marking NEW
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: crash, regression

Comment 3

14 years ago
WFM, 2003-11-10-05 trunk Linux
Summary: Crashes on attempt to print → Crashes on attempt to print [@ nsContainerFrame::SyncFrameViewAfterReflow]

Comment 4

14 years ago
WTF, Mozilla1.7b(installer with TB) and Xprint 009.

Comment 5

14 years ago
s/WTF/WFM/

Comment 6

14 years ago
WFM with linux trunk 2004032007 with Xprint and PS.

marking WFM
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
Crash Signature: [@ nsContainerFrame::SyncFrameViewAfterReflow]
You need to log in before you can comment on or make changes to this bug.