Closed Bug 564310 Opened 16 years ago Closed 15 years ago

[(Linux) 64-bit] Crash when AOL/AIM IMAP e-mail account with SavedIMs folder is accessed

Categories

(SeaMonkey :: MailNews: Backend, defect)

Product:
SeaMonkey
Component:
MailNews: Backend
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED INCOMPLETE

People

(Reporter: epp, Unassigned)

Details

(Keywords: crash, stackwanted)

User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100317 SeaMonkey/2.0.4 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.9) Gecko/20100317 SeaMonkey/2.0.4 Some AOL/AIM IMAP e-mail accounts will have a folder "SavedIMs". SeaMonkey 2.0.4 for Linux (x86_64) will crash completely if such an account is accessed via Mail & News. It will also crash if web browsing only and the backend checks such an account for new messages. Reproducible: Always Steps to Reproduce: 1. Access AOL/AIM IMAP e-mail account which includes a folder "SavedIMs". 2. SeaMonkey crashes immediately upon access. 3. Actual Results: SeaMonkey crashes upon accessing account as described. Expected Results: SeaMonkey should not have crashed. Using Ubuntu Linux 10.04 64-bit (amd64). I am aware that the 64-bit version of SeaMonkey is contributed, however it is not saving any crash reports. SeaMonkey versions 2.0.5 and 2.1a1pre (both 64-bit) also crash in the same manner as 2.0.4.
SM 2.0.3 (64-bit) also crashes in the same manner.
Can you reproduce with 32-bit SeaMonkey? (or (64-bit) Thunderbird?)
Keywords: crash
Version: unspecified → Trunk
The 32-bit version will not launch on 64-bit Ubuntu, a terminal window indicates "seamonkey-bin" isn't there, but it is... On 32-bit Ubuntu, the 32-bit SeaMonkey does not crash.
Summary: Crash when AOL/AIM IMAP e-mail account with SavedIMs folder is accessed → [(Linux) 64-bit] Crash when AOL/AIM IMAP e-mail account with SavedIMs folder is accessed
I ran it from a terminal and this is what the error file created when it crashed: $./seamonkey 2<&1 | tee /tmp/seamonkey-errors.txt (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead (seamonkey-bin:5721): Gdk-WARNING **: XID collision, trouble ahead Segmentation fault
You have installed flash player in the 64bit version? Which distribution do you use?
Using Ubuntu Linux 10.04 64-bit (amd64). There is a Flash plugin installed. At the time the software was first installed (Ubuntu 9.04), I used the 64-bit beta plugin of Flash that was available from the Adobe Labs web site.
If you disable all add-ons ( Tools - Add-On Manager ) and it works, it clearly indicates that the issue was caused by an add-on. You can try and enable each add-on step-by step and see what add-on is causing you trouble.
The only add-ons listed are ChatZilla, DOM Inspector and JavaScript Debugger, which I believe were all included with the SeaMonkey distribution by default. Out of these three, I have only used ChatZilla in the past.
This only occured with the 64-bit SeaMonkey, not on 32-bit. When the accounts were deleted and recreated using POP3 instead, SeaMonkey did not crash.
(In reply to comment #8) > If you disable all add-ons ( Tools - Add-On Manager ) and it works, it clearly > indicates that the issue was caused by an add-on. You can try and enable each > add-on step-by step and see what add-on is causing you trouble. The three add-ons were disabled and SeaMonkey restarted. During the first login of the IMAP account in question, SeaMonkey crashed again, so the add-ons are not causing the crashes.
Closing as INCOMPLETE since the original reporter did not provide a crash stack. Please reopen if you can get the SeaMonkey Crash Reporter to send one or more crash stacks to the Mozilla crash-stats server.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
Reporter, testing (Debug) 64-bit Thunderbird would help to confirm whether this is a SeaMonkey only or common MailNews issue. Reopen when you have new data, as I assume this bug would be nice to fix (if it hasn't been in the meantime). V.Incomplete ftb.
Status: RESOLVED → VERIFIED
I now use Debian 64-bit, but will check an AOL account that has this same folder to see whether Debian's Iceape and/or Icedove crash. I no longer use "testing" software, sorry.
You need to log in before you can comment on or make changes to this bug.