Closed Bug 15872 Opened 25 years ago Closed 25 years ago

[PP]Regression: Crash on clicking messages consecutively

Categories

(MailNews Core :: Backend, defect, P2)

Other
Linux

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: fenella, Assigned: scottputterman)

Details

Linux (1999-10-07-16-M10)
Steps.
1. Launch Messenger
2. Select the IMAP account, click on the Inbox
3. Click on the messages consecutively

Actual result: Sometimes it crashes on the 2nd message, sometime the 4th,
sometimes on the 5th or 6th. Eventually it will crash if I keep select messages.

Expected result: it should not crash.

This happens on Linux IMAP only.
It does not occur on Win32 or Mac.

I do not get a core file. But some error message comes up in the console
window.
Init!

adding "http://cvs-mirror.mozilla.org/webtools/tinderbox/SeaMonkey/flash.rdf" to
the tree
http://cvs-mirror.mozilla.org/webtools/tinderbox/SeaMonkey/flash.rdf: setting
poll interval to 300sec.
adding "rdf:msgnotifications" to the tree
adding "rdf:xpinstall-update-notifier" to the tree
an exception occurred trying to load "rdf:xpinstall-update-notifier":
[Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE)
[nsIRDFService.GetDataSource]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"
location: "JS frame :: chrome://sidebar/content/flash.js :: FlashInit :: line
79"  data: no]

imap://fenella@nsmail-2/INBOX
commonDialogOnLoad
Summary: [PP]Regression: Crash on clicking message consecutively → [PP]Regression: Crash on clicking messages consecutively
If I select the message, read it and then click on another message, it does not
crash as frequently.
Assignee: phil → putterman
Priority: P3 → P2
Target Milestone: M11
Tree issue? Over to putterman. P2/M11
does this still happen?
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Status: RESOLVED → VERIFIED
Linux (1999-10-29-10M11)
This problem does not exists any more. Mark it Worksforme
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.