100809 - Printing a page => crash [@ nsTableRowGroupFrame::InitRepeatedFrame ]

Status: RESOLVED INVALID

(Core :: Printing: Output, defect, P1)

Description

[(Don't use, old account) - Kai Engert]

Build ID 2001092000 (094 branch).

Go to above URL. Print.
I used options: Last page first, Grayscale, A4, All pages, all borders set to 0.5.

Crash.

Comment 1

[(Don't use, old account) - Kai Engert]

reproducable: always

Comment 2

[(Don't use, old account) - Kai Engert]

crash keyword

Will attach stack trace of crash. It crashes in
nsTableRowGroupFrame::InitRepeatedFrame, originalRowFrame is NULL, this method
doesn't make a null check.

Comment 3

[(Don't use, old account) - Kai Engert]

Attachment: stack trace

Comment 4

[rods (gone)]

This asserts in the nsBulletFrame.h for me on the tip. Over to layout

Comment 5

[Olivier Cahagne]

wfm using build 2001103113 on Linux.

Comment 6

[Kai Engert [:KaiE:]]

I'm still crashing.

But I'm very happy to say that I found a way to reproduce it. The crash depends
on some old settings that have survived in my profile.

On Linux: Close Mozilla, open your prefs.js file from your profile directory,
and insert the following line:

user_pref("browser.display.screen_resolution", 96);

Save, start Mozilla, go to the above listed URL, print, crash.

This cost me an hour to track it down. I think old profile settings shouldn't be
able to crash the application.

Comment 7

[Marc Attinasi]

--> P1

Comment 8

[Marc Attinasi]

That setting causes a total hang for me on Linux - no stack trace.  In fact, the
entire X-server seems to hang and I had to unplug the machine. Very nice.

I think Rod's assignment to layout was too hasty.  There is a serious problem
with the way that the resolution is being used.  I'll reassign to Pavlov since
he knows a lot about GTK (and I know nothing).

Comment 9

[Kai Engert [:KaiE:]]

I think a crash should not be future, back to 0.9.9

Comment 10

[Stuart Parmenter]

DO NOT RETARGET OTHER PEOPLES BUGS.
-> FUTURE.

Comment 11

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

That pref should work (although I've been planning to make it work on other
platforms, too -- see bug 69205).  Perhaps I should own this bug, although I
wouldn't be able to get to it for quite a while, if ever.

This may well be related to bug 103145.

Comment 12

[Kai Engert [:KaiE:]]

Does this preference have any effect right now? I don't see a control in
preferences, so user's won't be able to control it anyway.

Should we, until we have time to analyze this, create a simple patch that simply
ignores this preference?

Comment 13

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

It's at the bottom of Preferences|Appearance|Fonts.

Comment 14

[Aleksander Adamowski]

I crash on Linux with 2002022806-trunk when I go to
http://www.software.com.pl/DevCon/ and print.

To reproduce I go through following steps:
1. go to http://www.software.com.pl/DevCon/
2. select File->Print, click OK (print properties have no significance)
3. experience a crash

Can you please extract stacktraces from my talkback reports and check whether
their signatures match this bug?
TB3475650H
TB3475461M

Comment 15

[Aleksander Adamowski]

Hmm... I think I'm seeing something new, because I don't crash prining
http://www.robval.com/linux/desktop/index.asp

Comment 16

[Aleksander Adamowski]

Filed bug 128501 for the new crash.

Comment 17

[Benoit Mortier]

crash when printing from http://www.sospsy.com/Biblio9/biblio045.htm

Reproduct this

1.Go to the url
2.Select File->Print
3.Crash

Configuration
Red Hat 7.2 with all the patches
Kde 2.2.2
Mozilla 0.9.9 from RPMS
Mozilla version 2002031115

Comment 18

[Adam Cioccarelli]

This and many other pages crash mozilla when printing for me. Build ID 2002041409
Linux 2.4.18-xfs

Is it a problem with the backend? I'm using CUPS.

Comment 19

[Aleksander Adamowski]

Adam, can you see whether you crash on this page:
http://olo.office.altkom.com.pl/domowa/mozilla/iframe_print/

If yes, you may want to have a look at bug 128501.

Comment 20

[Adam Cioccarelli]

Hi Aleksander,

yes this crashes my browser! I first get the message "printing failed for some
unknown reason", I click OK and..... crash

TB5288964Z

Comment 21

[Adam Cioccarelli]

Does this mean that it is a duplicate of 128501?

Comment 22

[Aleksander Adamowski]

Adam: not likely since I can reliably repro bug 128501, but cannot repro this bug.

You just can repro both of them...

We have a problem determining what configuration is needed to reproduce bug
128501, maybe you could help...

Comment 23

[Prof J C Nash]

Under Win98 SE on Pentium 3, 1GHz, Mozilla 0.9.9 and 1.0 (build 20020417) crash
when trying to print to Acrobat
PDF writer (vn 4.05) and sometimes to Docucom PDF writer vn 4.61. Sometimes an
"out of memory" message is displayed (I've 256MB). Sometimes "Illegal operation".
Very annoying -- sometimes everything is locked, other times, the Mozilla task
can be ended. 

Comment 24

[Olivier Cahagne]

URL has disappeared, no testcase, propose to resolve as invalid or wfm.

Comment 25

[Kenneth Herron]

The sample URL now points to a domain-for-sale page. Resolving invalid because
there's no way to test it. In fact the problem was probably fixed by bug 120364
or bug 207145.