202515 - Mail & Newsgroups / Composition options crashes mozilla since bugfix for 107877 was added.

Status: VERIFIED FIXED

(SeaMonkey :: Preferences, defect)

Description

[Frederic Bezies]

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

Since last wednesday, when bugfix for 107877 was added, everytime I want to go
to Mail & Newsgroups / Composition option, Mozilla quits without warning.

I am using a trunk based build Mozilla (lastest sources available) ; my build
option are --enable-crypto, --enable-xft, --disable-tests and --disable-debug.

I am sorry if this bug had been reported before.

Reproducible: Always

Steps to Reproduce:
1.Go to Preferences / Mail & Newsgroups
2.Click on composition line

Actual Results:  
Mozilla quits without warning.

Expected Results:  
Seeing options

Comment 1

[Mitch]

Please enable debug and provide a stacktrace of your crash.

Perhaps a dup of bug 202439

Comment 2

[Frederic Bezies]

Ok. I will try to see with --enable-debug and a CVS updated source as soon as
possible.

Comment 3

[Frederic Bezies]

Attachment: crash log

Here is the log when launching debug-enabled based build.

I just go to Edit/Preferences / mail & Newsgroups and click on Compose.

Do you want gdb output ? How to make a stacktrace ? Sorry for this basic
question :-|

Comment 4

[Boris Zbarsky [:bzbarsky]]

Crash in xft code

Comment 5

[Frederic Bezies]

So, my thought was good. I thought xft was guilty here. I also noticed this bug
happens (quitting without warning) if in an account, html is on by default and
you want to compose a message.

Thanks for finding the guilty component.

Comment 6

[Christopher Blizzard (:blizzard)]

I just fixed this on the trunk before I saw this bug.

Comment 7

[Frederic Bezies]

Thanks for fixing it.

Comment 8

[sairuh (rarely reading bugmail)]

not a problem with today's build on linux.

Comment 9

[Christopher Blizzard (:blizzard)]

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