318890 - [trunk] mailnews and chatzilla keeps on crashing SeaMonkey

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect)

Description

[Frederic Bezies]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: 

A recent regression appears in SeaMonkey. I build it in order to see the new artwork, and since that mailnews and chatzilla keeps on crashing.

In a yesterday homemade build I cannot see this bug.

Reproducible: Always

Steps to Reproduce:
1.Build seamonkey with a CVS up-to-date source
2.Launch SeaMonkey
3.Click on chatzilla or mailnews traybar icon

Actual Results:  
SeaMonkey crash

Expected Results:  
Launching chatzilla or mailnews.

I deleted my caches, and I am using either modern or classic theme.

Comment 1

[Ruediger Lahl]

(In reply to comment #0)

> A recent regression appears in SeaMonkey. I build it in order to see the new
> artwork, and since that mailnews and chatzilla keeps on crashing.

I can confirm that crash for the Trunk on Win-XP and Linux.

Last good CREATURE-build on my system is 2005120214. First bad here is 2005120223

Can you please change 'Hardware' and 'OS' to All?

Comment 2

[Ruediger Lahl]

(In reply to comment #1)

> I can confirm that crash for the Trunk on Win-XP and Linux.
> 
> Last good CREATURE-build on my system is 2005120214. First bad here is
> 2005120223

Okay, 2005120301 works fine again.

Comment 3

[Wayne Mery (:wsmwk)]

does it happen with a nightly trunk build and if so can you cite a talkbackid for the crash?

Comment 4

[Ruediger Lahl]

(In reply to comment #3)

> does it happen with a nightly trunk build and if so can you cite a talkbackid
> for the crash?

With the WinXP-Tinderbox-build 2005120223. I think this builds don't have talkback, so no ID exists. But the bug is allready fixed.

Comment 5

[Frederic Bezies]

Indeed, it is fixed. Maybe an half checking crash or something related.

Closing it as fixed.

Comment 6

[Stefan [:stefanh]]

--> wfm, we don't know what fixed this.

Comment 7

[Ruediger Lahl]

(In reply to comment #6)
> --> wfm, we don't know what fixed this.

Seems it was the patch for: https://bugzilla.mozilla.org/show_bug.cgi?id=318873