If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Printing certain html crashes the browser (exit 11)

RESOLVED WORKSFORME

Status

()

Core
Printing: Output
RESOLVED WORKSFORME
15 years ago
15 years ago

People

(Reporter: Danek Duvall, Assigned: rods (gone))

Tracking

({stackwanted})

Trunk
stackwanted
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

15 years ago
Mozilla, built 2003021815 on Solaris, shows this behavior as well when trying
to print the html file attached in the next comment.  I've tried to trim it down
as much as possible, but it seems that it's the structure that's important, as
well as some of the spacing.  I see the same problem with 2003022500 on Linux,
as well as an older, December build, on Solaris.
(Reporter)

Comment 1

15 years ago
Created attachment 115598 [details]
Printing this file crashes the browser

Comment 2

15 years ago
Created attachment 115600 [details]
attachment 115598 [details] printed using 2003-02-25-08-trunk + Xprint module (300 DPI, DIN-A4)

WTF when printing with 2003-02-25-08-trunk using Xprint module.

Reporter:
1. Can you try a newer build and/or printing with Mozilla's Xprint module (see
http://www.mozilla.org/releases/mozilla1.2.1/index.html#xprint for details)
2. Can you provide a stacktrace from the coredump ?

Updated

15 years ago
Keywords: stackwanted

Comment 3

15 years ago
this actually looks like bug 191339.  I crashed with linux trunk build
2003022405, but now 2003022508 works fine (bug 191339 was fixed during that window)

testcases look somewhat similar.

Danek, are you sure the 20030225 Linux build works?
(Reporter)

Comment 4

15 years ago
****.  Sorry for the bogus bug.  It does in fact work with a build from midnight
today.  I'd neglected to fully test it this morning because my original test
case was a page past a login screen, and a broken profile wouldn't let me past
that screen.  So all my data points were from older builds.

Roland: there wasn't actually a core file -- it exited with exit code 11, not
signal 11.  I found that strange too, and made sure.
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.