205530 - multiple forward = segmentation fault

Status: RESOLVED WORKSFORME

(Core :: Layout, defect)

Description

[Bob Lockie]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030513
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030513

select multiple messages and then selecting the forward button result in all the
mozilla windows closing.
Running from a telnet shows:
/usr/local/mozilla/run-mozilla.sh: line 72:  1550 Segmentation fault     
"$prog" ${1+"$@"}


Reproducible: Always

Steps to Reproduce:
1. highlight multiple (2) messages.
2. select the "Forward" button.


Actual Results:  
All the mozilla windows close (mail, browser, everything).

Expected Results:  
Multiple messages should have been forwarded (either one compose window
containing all the messages (preferred) to forward or multiple compose windows).

Comment 1

[Matthias Versen [:Matti]]

Reporter:
Do you have a Talkback ID from that crash ?

Comment 2

[Andrew Schultz]

Attachment: stacktrace

Time to create the composition window WITH a body!!!!
WEBSHELL+ = 5
Time to create the composition window WITH a body!!!!
WEBSHELL+ = 6
###!!! ASSERTION: CachedChromeStream doesn't receive data: 'Not Reached', file
nsXULDocument.cpp, line 4401
Break: at file nsXULDocument.cpp, line 4401
WARNING: NS_ENSURE_TRUE(window) failed, file nsContentTreeOwner.cpp, line 643
WARNING: NS_ENSURE_TRUE(docShellElement) failed, file nsXULWindow.cpp, line
1186
WARNING: NS_ENSURE_TRUE(docShellElement) failed, file nsXULWindow.cpp, line
1206
WARNING: NS_ENSURE_TRUE(windowElement) failed, file nsXULWindow.cpp, line 1240
###!!! ASSERTION: no xul:window: 'windowElement', file nsXULWindow.cpp, line
983
Break: at file nsXULWindow.cpp, line 983
###!!! ASSERTION: no xul:window: 'windowElement', file nsXULWindow.cpp, line
1055
Break: at file nsXULWindow.cpp, line 1055
WARNING: NS_ENSURE_TRUE(windowElement) failed, file nsXULWindow.cpp, line 893
Gdk-ERROR **: BadValue (integer parameter out of range for operation)
  serial 8225 error_code 2 request_code 12 minor_code 0
Gdk-ERROR **: BadValue (integer parameter out of range for operation)
  serial 8226 error_code 2 request_code 12 minor_code 0

Comment 3

[Andrew Schultz]

further investigation shows that it is necessary to set the following prefs to
experience this bug:
forward messages: inline (not as attachments)
compose messages in HTML format *not* checked

marking NEW

Comment 4

[Bob Lockie]

Interesting, it never runs talkback.
Is that another bug?

Comment 5

[Andrew Schultz]

for me, it usually triggers a gdk error. gdk recognizes a problem, prints a
message and bails, taking Mozilla with it.  talkback doesn't have a chance.

Comment 6

[Wolfgang Rosenauer [:wolfiR]]

*** Bug 216519 has been marked as a duplicate of this bug. ***

Comment 7

[Mats Palmgren (inactive)]

*** Bug 225954 has been marked as a duplicate of this bug. ***

Comment 8

[Aleksey]

*** Bug 226115 has been marked as a duplicate of this bug. ***

Comment 9

[chris hofmann]

if we get close to a fix for this for 1.6 re-nominate

Comment 10

[Asa Dotzler [:asa]]

*** Bug 195892 has been marked as a duplicate of this bug. ***

Comment 11

[Andrew Schultz]

Attachment: stacktrace with --sync

DocumentViewerImpl does an unconstrained reflow, which sets the size to 2^30 by
2^30.  It then converts that to pixels and attempts to actually resize the
content (which happens to be a window) to that size.

Comment 12

[David :Bienvenu]

Is this bug still in 1.7 or 1.8?

Comment 13

[Andrew Schultz]

yes (the stack was from current CVS).
bz on irc said this looked like a layout issue.

==> layout

Comment 14

[Mats Palmgren (inactive)]

WFM, SeaMonkey 2005-08-31-02 trunk Linux.  (fixed by bug 293781?)

Comment 15

[Boris Zbarsky [:bzbarsky]]

Possible...

Comment 16

[Christian Krause]

I can't reproduce the problem with mozilla 1.7.11 - it seems, that the bug is
fixed. 
But I don't know, whether the mentioned fix of the other bug was checked into a
trunk from which mozilla 1.7.11 was built. Unfortunately I can't install an
older version for a "double-check" at the moment.

Comment 17

[Christopher Schultz]

This now WFM in tb 1.0.7. Using "in-line" forwarding results in separate messages being created for each message, "attached" forwarding results in a single message with all forwarded messages as attachments to the one message.

Comment 18

[Seva Gluschenko]

after all, creating multiple windows when forwarding inline is NOT desired behaviour. There should be an option to forward them in one message.

Comment 19

[Boris Zbarsky [:bzbarsky]]

This bug is worksforme.  Please take discussion about how mail should work to a mail bug (this one is a layout engine bug).