121131 - Crash when changing font size on "Print Preview" screen

Status: RESOLVED INVALID

(Core :: CSS Parsing and Computation, defect)

Description

[Kim Scarborough]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.7+ 
Gecko/20020121

BuildID:    2002012103

When I bring up a page in "Print Preview" that's going to be more than one 
printed page and then change the font size under "Text Zoom" (either smaller or 
larger), it crashes. If the page being previewed is just one printed 
page, "Text Zoom" works (although it renders bizarrely, but that's another bug 
report).

Reproducible: Always
Steps to Reproduce:
1. Load a page that you know will take more than one page to print
2. Go to File -> Print Preview
3. Go to View -> Text Zoom -> Smaller (or Larger)


Actual Results:  It go boom

Expected Results:  Changed the font size on the display (and on the printout, 
presumably)

I've sent a couple Talkback reports on this, but I'm not sure how to get the 
crash ID.

Comment 1

[Karl Johan Kleist]

Build ID: 2002 01 11 03. Windows 2000.

I can reproduce the crash. Incident ID: TB1937796Z

Comment 2

[Boris Zbarsky [:bzbarsky]]

Happens on linux current CVS too.  When loading, I see lots of:

###!!! ASSERTION: running past end: 'mCurrent != mListLink', file nsLineBox.h,
line 552
###!!! Break: at file nsLineBox.h, line 552

Then when changing font size,

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1024 (runnable)]
0x41451273 in nsStyleContext::ClearStyleData (this=0x88d0fcc,
aPresContext=0x88831d0, 
    aRule=0x0) at nsStyleContext.cpp:608
608           child->ClearStyleData(aPresContext, aRule);
Current language:  auto; currently c++

#0  0x41451273 in nsStyleContext::ClearStyleData (this=0x88d0fcc, 
    aPresContext=0x88831d0, aRule=0x0) at nsStyleContext.cpp:608
#1  0x414512c8 in nsStyleContext::ClearStyleData (this=0x88d0ec4, 
    aPresContext=0x88831d0, aRule=0x0) at nsStyleContext.cpp:616
#2  0x41451288 in nsStyleContext::ClearStyleData (this=0x88d0960, 
    aPresContext=0x88831d0, aRule=0x0) at nsStyleContext.cpp:608
#3  0x41451288 in nsStyleContext::ClearStyleData (this=0x88d0664, 
    aPresContext=0x88831d0, aRule=0x0) at nsStyleContext.cpp:608
#4  0x41451288 in nsStyleContext::ClearStyleData (this=0x88d0500, 
    aPresContext=0x88831d0, aRule=0x0) at nsStyleContext.cpp:608
#5  0x41451288 in nsStyleContext::ClearStyleData (this=0x88d0318, 
    aPresContext=0x88831d0, aRule=0x0) at nsStyleContext.cpp:608
#6  0x41451288 in nsStyleContext::ClearStyleData (this=0x88465f8, 
    aPresContext=0x88831d0, aRule=0x0) at nsStyleContext.cpp:608

(gdb) frame 0
#0  0x41451273 in nsStyleContext::ClearStyleData (this=0x88d0fcc, 
    aPresContext=0x88831d0, aRule=0x0) at nsStyleContext.cpp:608
608           child->ClearStyleData(aPresContext, aRule);
(gdb) p child
$1 = (nsStyleContext *) 0x1
(gdb) p *child
Cannot access memory at address 0x1
(gdb) p mChild
$7 = (nsStyleContext *) 0x1

Looks like someone appended a weird style context at some point...

Comment 3

[Boris Zbarsky [:bzbarsky]]

Attachment: full stack

Comment 4

[Ludovic Hirlimann]

Is this bug related to 121091 ?

Comment 5

[Boris Zbarsky [:bzbarsky]]

Unlikely.  Look at the stacks; they have pretty much nothing in common.

Comment 6

[rcummins]

Is this bug still valid now that Print Preview implements its own toolbars? 
I.e. you can no longer change the font size while previewing?

Comment 7

[Kim Scarborough]

No, looks like the new controls fixed this (and introduced a new bug, but that's
for another report). Go ahead and close this.

Comment 8

[Boris Zbarsky [:bzbarsky]]

Note that this is a crash in the style system (not in the print code) that may
be triggerable under other circumstances than print preview....

Comment 9

[Madhur Bhatia]

checked in builid: 2002/04/15-10trunk on win2000

Since, the print preview layout has changed, the steps mentioned in the original 
comment are not reproducable. In the print preview page there are no more menu 
options (no View -> Text Zoom options).
Marking this bug invalid with respect to the new layout.

Please reopen if anyone thinks otherwise. Thx!