Closed
Bug 20247
Opened 25 years ago
Closed 25 years ago
[DOGFOOD][CRASH] Open IMAP folder after read/unread flag changed
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
People
(Reporter: rzach, Assigned: Bienvenu)
Details
(Whiteboard: [PDT-])
Mozilla crashes when I try to reopen an IMAP folder which has been changed in the interim. To reproduce: 1. Open messenger 2. Open IMAP folder 3. Close messenger 4. From a separate program (I used Navigator 4.7), change the read/unread flag on a message. 5. Close the folder. 6. Open messenger again 7. Open the folder again Actual outcome: Crash Expected outcome: The folder contents should be displayed with theflag changed Observed on: Linux builds 1999.11.15.20 and 1999.11.28.08, running on RH 6.0
Severity: major → critical
Summary: [CRASH] Open IMAP folder after read/unread flag changed → [DOGFOOD][CRASH] Open IMAP folder after read/unread flag changed
Updated•25 years ago
|
Assignee: phil → bienvenu
Comment 1•25 years ago
|
||
David, can you look at this?
Assignee | ||
Comment 2•25 years ago
|
||
this works fine for me. I'd need to know what server is being used, and a stack trace would be nice.
Reporter | ||
Comment 3•25 years ago
|
||
This happens on mail.math.berkeley.edu; it does not happen on another IMAP server I tried, uclink4.berkeley.edu. Stack trace (I don't really know how to do this--I didn't get a core dump, so I did ./mozilla -g; send me email if you need something else): imap://zach@mail.math.berkeley.edu/INBOX In ChangeFolderByURI [New Thread 2979] In reroot folder before clearItemSelection in showthreads Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 2965] Program received signal SIGSEGV, Segmentation fault. 0x894dad3 in ?? () from /usr/lib/libgdk_imlib.so.1 (gdb) bt #0 0x894dad3 in ?? () from /usr/lib/libgdk_imlib.so.1 #1 0x400f0bab in nsThread::~nsThread () #2 0x400f0ccd in nsThread::Release () #3 0x400f0c26 in nsThread::Exit () #4 0x40126bd3 in _PR_DestroyThreadPrivate () #5 0x401353b0 in PR_Sleep () #6 0x4014b560 in __pthread_destroy_specifics () at specific.c:152 #7 0x4014852e in pthread_exit (retval=0x0) at join.c:36 #8 0x40148cef in pthread_start_thread () at manager.c:207
Putting on PDT- since no reproducible case. If you get one, remove PDT- and we will re-evaluate at pdt mtgs.
Assignee | ||
Comment 6•25 years ago
|
||
Are you leaving the mozilla app running when you use a second app to mark a message read? My theory is that you're using an imap server that only allows a single connection to a folder, and kills previous connections (like the UW server). This would expose you to bug #18005
Reporter | ||
Comment 7•25 years ago
|
||
I close the mail window, but the browser window stays open. Telnetting to my server at port 153 says: OK yuban-c.math.berkeley.edu IMAP4rev1 v12.254 server ready While the other server, where the problem doesn't arise, says OK uclink4.berkeley.edu Execmail IMAP4rev1 (2.1.1/199902261402) Maybe you can tell from that what IMAP servers are running there.
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Comment 8•25 years ago
|
||
looks like UW to me. Marking a dup of 18005. *** This bug has been marked as a duplicate of 18005 ***
Assignee | ||
Comment 9•25 years ago
|
||
I think you'll get notified by bugzilla when 18005 is fixed - it would be great if you could try again after that. I'll try to remember to remind you as well. Karen, this is a good test case to try, with the UW server and the mailbox format that only allows one connection to a folder.
Assignee | ||
Comment 10•25 years ago
|
||
Oh, and to any doubters, this has the same stack trace as 18005
Updated•25 years ago
|
QA Contact: lchiang → huang
Comment 11•25 years ago
|
||
Change QA Contact to me. Cc: Lisa.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 12•25 years ago
|
||
Since this bug is duplicate of bug#18005 Will wait for the fix of bug#18005 to verify. Mark as verified!
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•