1416272 - CRASH when launch Email Client

Status: RESOLVED DUPLICATE of bug 1401528

(SeaMonkey :: MailNews: General, defect)

Description

[Rainer Bielefeld]

Steps how to reproduce with unzipped installer of  official en-US SeaMonkey 2.55a1 (NT 6.1; WOW64; rv:58.0) Gecko/20100101 Firefox/58.0 Build 20171110010345  (Default Classic Theme) on German WIN7 64bit:

1. Launch Browser
2. Click menu ˋWindow → Mail & Newsgroupsˊ
   CRASH

a) also happens in safe mode.

b)  Crash Report ID:
    bp-5dbf0b33-ef7a-4fa3-8d79-4fe250171110
    bp-04ea8edc-7364-48c2-ba8a-0908e0171110
    bp-39f37e66-dbfa-4316-abb7-b3a520171110
    bp-fb9bcd93-babe-4d9e-8443-3fdc40171023

c) Crash Reason: EXCEPTION_ACCESS_VIOLATION_READ

Comment 1

[Frank-Rainer Grahl (:frg)]

Dupes to Bug 1360803 but just might be a dupe of bug 1408682

Comment 2

[Rainer Bielefeld]

(In reply to Rainer Bielefeld from comment #0)
The only information I can tell is that TB Daily 56.0a1 (2017-07-30) (64-bit) works fine for me.

Comment 3

[Rainer Bielefeld]

2.56 also is affected, but that one doesn't always crash immediately, sometimes I can do some (few) actions before it crashes.

Comment 4

[K Chayka]

Mail has been crashing for me on nightlies since the past 2+ months: 2.54, 2.55 and 2.56. This morning tried the latest Win build (20171125 2.56 Win32 build running on Win10 Pro 64-bit) with a new profile.
1. Download zip and uncompress to a new folder
2. Start Seamonkey and create a new profile
3. Add 1 POP3 email account, using SSL/TLS authentication (port 995), normal password, no automatic "get messages" (to better control testing)
4. Send a test message to the account by any means other than this Seamonkey mail-news (because it's broken)
5. Switch to mail-news window. At this point the thread-pane is blank
6. Click Get Messages in the toolbar - the folder pane shows an unread message in the inbox and the thread-pane is still blank
7. Click on Inbox in the folder pane

Crash. Restarting the browser, opening mail-news and clicking on Inbox always results in a crash. Sent 2 crash reports this morning.
bp-71b4ae74-d112-4825-a33b-cf0e70171125
bp-b2e17e8f-ed9d-4809-b17c-5adc50171125

Comment 5

[K Chayka]

My crash reasons were also "EXCEPTION_ACCESS_VIOLATION_READ"

Comment 6

[Frank-Rainer Grahl (:frg)]

Could you try to set jsloader.shareGlobal to false as a workaround.

TB set it as a workaround for bug 1401528.

Works for me in a private build with a ton of fixes which are not ready for prime time or review yet. Even even with them 2.56 is not good for much thanks to Mozilla breaking almost all add-ons with code removals.

FRG

Comment 7

[K Chayka]

(In reply to Frank-Rainer Grahl (:frg) from comment #6)
> Could you try to set jsloader.shareGlobal to false as a workaround.

That worked after Seamonkey restarted. Successfully read and replied to the test message. Thanks!

Comment 8

[Frank-Rainer Grahl (:frg)]

So lets dupe the bug to Bug 1401528. If this one is fixed please unset the pref. If SeaMonkey still crashes with the same error please reopen. Otherwise it is probably a new bug elsewhere.