Closed Bug 1009427 Opened 12 years ago Closed 12 years ago

Attempting to access a particular e-Mail in the Inbox causes Seamonkey to crash

Categories

(SeaMonkey :: MailNews: Message Display, defect)

SeaMonkey 2.29 Branch
x86_64
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: se014a0001, Unassigned)

References

()

Details

Crash Data

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0 SeaMonkey/2.29a1 (Beta/Release) Build ID: 20140512230917 Steps to reproduce: Clicking on any but the top e-Mail in the list causes Seamonkey to crash. Actual results: Seamonkey crashed ... example crash report http://crash-stats.mozilla.com/report/index/bp-117ca650-99f6-4f4d-8a5b-3c1a02140513 The crash location in libc-2.15.so is abort() (identified by checking the address against nm -D libc-2.15.so). The last Seamonkey routine in the stack trace is (identified by checking the address against nm -D libxul.so) is _Z24JS_GetDataViewByteLengthP8JSObject. Expected results: It should be possible to do things with mail! I first had a problem with a build from 6th May. http://crash-stats.mozilla.com/report/index/bp-6b528264-bc0f-4da9-8093-b77b32140512 I updated to last night, and now I can't do anything with it :(. I was able to compress the Inbox, but it has made no difference.
Apologies, I think the crash is associated with one particular e-Mail. All attempts to navigate to it in the list cause Seamonkey to crash. It just happened to be the second in the list. It is a junk mail from National Geographic with an attachment. I can deal with other e-Mails with attachments, just not this one. I can't get at it from Seamonkey, but there are other ways. Would it be helpful to attach it? A particular e-Mail crashes the e-Mail reader; could this be a security bug?
Flags: sec-review?
Summary: Attempting to access any but the top mail in the Inbox causes crash → Attempting to access a particular e-Mail in the Inbox causes Seamonkey to crash
I've found another e-Mail in my Inbox that produces the same crash. This has been labelled as Junk, and has no attachments.
I have now found a URL that causes a crash with the same ultimate signature, and the last address in libxul.so looks to be in the same routine, although I have just updated my build as of a few minutes ago. The URL is http://ojp.nationalrail.co.uk/service/planjourney/search
Severity: normal → critical
Crash Signature: [@ libc-2.15.so@0x36425 ] => abort(), apparently from somewhere in _Z24JS_GetDataViewByteLengthP8JSObject, although the call stack is deep. See ID: b76d9be8-6f7e-4cbb-9c5e-8f64f2140516
> Crash Signature: [@ libc-2.15.so@0x36425 ] => abort(), apparently from somewhere > in _Z24JS_GetDataViewByteLengthP8JSObject, although the call stack is deep. See > ID: b76d9be8-6f7e-4cbb-9c5e-8f64f2140516 https://crash-stats.mozilla.com/report/index/b76d9be8-6f7e-4cbb-9c5e-8f64f2140516
Crash Signature: [@ libc-2.15.so@0x36425 ] => abort(), apparently from somewhere in _Z24JS_GetDataViewByteLengthP8JSObject, although the call stack is deep. See ID: b76d9be8-6f7e-4cbb-9c5e-8f64f2140516 → [@ libc-2.15.so@0x36425 ]
It's fixed! Thankyou.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.