Closed Bug 43374 Opened 25 years ago Closed 25 years ago

Deleting messages bottom upward causes thread pane problems.

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

Product:
SeaMonkey
Component:
MailNews: Message Display
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: laurel, Assigned: hyatt)

References

Details

(Keywords: crash, topcrash, Whiteboard: [nsbeta2+]Verified worst symptoms/crash 7/31 all platforms.)

Using jun21 m17 commercial build, all platforms found while verifying bug #21633 When deleting messages individually in sequence beginning at the bottom of the thread pane, considerable display problems with the thread pane occur. Problems may vary depending on the window/thread pane size. 1. Go to mail window, open a mail folder (POP or IMAP) having lots of messages (I used 100+). 2. I was in a default date sort, message pane shown. 3. Move the thread/msg pane splitter upward so there are about 10 messages shown in the thread pane. 4. Scroll to bottom of thread pane. 5. Select last/bottom message in thread pane, Delete it. 6. Repeat to delete individual messages in sequence upward in thread pane until you've deleted all (10) messages in the original display area. 7. Thread pane needs to scroll upward. Keep deleting... Result: Varied results, always eventual thread pane problems. Some problems witnessed in jun21 commercial build include: -- blank line appears at top of thread pane way before you've deleted all the initially displayed messages -- thread pane scrollbar disappears and doesn't always return -- duplicate messages shown -- multiple selections in thread pane, sometimes contiguous and sometimes non-contiguos -- thread pane message lines squish together horizontally (many message subjects on one line, can't read) -- no selection at all.
QA Contact: lchiang → laurel
I am going to nominate for nsbeta2. Since the problem occurs / is visible with the delete mail operation, I'm worried that the user may get into this state and not recognize what is happening and accidentally delete a message that is not intended to be deleted. The user can go to trash folder to recover, but not if the user is using the IMAP delete model (which deletes immediately) or if using the AOL IMAP server (which does not have a trash folder). Also, undo may be a workaround, but undo will only undo the last delete, I believe.
reassigning to hyatt. I'm pretty sure this is a tree widget bug. When I get into this state, scrolling up using the up arrow seems to not work either.
Assignee: putterman → hyatt
nominating beta3. I keep hitting this and it's ugly. I'm not sure what happened to Lisa's beta2 nomination -- she mentioned it, but it never was entered in keyword.
Keywords: nsbeta3
updating. I ran into this today on win32 2000-13-09-m17. I have a stack trace. In my case, when I get into this situation, I scrolled upwards in the thread pane. If the problem with getting into this strange state as laurel describes can be fixed, then perhaps the scrolling crash would never occur. nsXULTreeOuterGroupFrame::FindPreviousRowContent [d:\builds\seamonkey\mozilla\layout\xul\base\src\nsXULTreeOuterGroupFrame.cpp, line 816] nsXULTreeOuterGroupFrame::InternalPositionChanged [d:\builds\seamonkey\mozilla\layout\xul\base\src\nsXULTreeOuterGroupFrame.cpp, line 497] nsXULTreeOuterGroupFrame::PositionChanged [d:\builds\seamonkey\mozilla\layout\xul\base\src\nsXULTreeOuterGroupFrame.cpp, line 456] nsSliderFrame::SetCurrentPosition [d:\builds\seamonkey\mozilla\layout\xul\base\src\nsSliderFrame.cpp, line 692] nsSliderFrame::HandleEvent [d:\builds\seamonkey\mozilla\layout\xul\base\src\nsSliderFrame.cpp, line 471] PresShell::HandleEventInternal [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 3925] PresShell::HandleEvent [d:\builds\seamonkey\mozilla\layout\html\base\src\nsPresShell.cpp, line 3843] nsView::HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 782] nsViewManager2::DispatchEvent [d:\builds\seamonkey\mozilla\view\src\nsViewManager2.cpp, line 1389] HandleEvent [d:\builds\seamonkey\mozilla\view\src\nsView.cpp, line 69] nsWindow::DispatchEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 564] nsWindow::DispatchWindowEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 581] nsWindow::DispatchMouseEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3689] ChildWindow::DispatchMouseEvent [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 3894] nsWindow::ProcessMessage [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 2809] nsWindow::WindowProc [d:\builds\seamonkey\mozilla\widget\src\windows\nsWindow.cpp, line 830] USER32.dll + 0x1268 (0x77e71268) 0x013903f9
Severity: normal → major
marking relnote2, crash. Marking crash since subsequent user action after this behavior is observed results in crashes.
Keywords: crash, relnote2
*** Bug 45943 has been marked as a duplicate of this bug. ***
*** Bug 45995 has been marked as a duplicate of this bug. ***
adding self to cc-list - this bug happens to me every couple minutes.
This bug should be nsbeta2+. Nominating.
Keywords: nsbeta2
I have a fix in hand.
Whiteboard: Fix in hand. Give the word.
Awesome. Adding a few PDT people to, I hope, get approval tonight. This will make my mail use so much easier! The main symptom I see is the thread pane just stops painting, and I have to close down the window and reopen it every couple minutes. I think we have to accept this fix.
Would it be reasonable to ask some folks to run with this fix for a day or two and then decide whether to take it on the branch? I'm nervous about taking this on the day before we try to branch unless we have a super-high confidence level.
I'm happy to try running with a patch. I should be able to tell quickly if it makes things better.
Putting on [nsbeta2+] radar....check 'er in!
Whiteboard: Fix in hand. Give the word. → [nsbeta2+]Fix in hand. Give the word.
this stacktrace made it to the topcrash report this morning. rapid scrolling in bookmarks also appears to surface the crash. deleting the last message in the threadpane is another test case to check out with the fix. Here are comments from the top crash report. 2000072409 CrashDate: 2000-07-24 UptimeMinutes: 16 Total: 68 OS: Windows NT 5.0 build 2195 URL: Comment: scrolling "viciously" in the bookmarks manager (grab and drag up and down rapidly). Build: 2000072409 CrashDate: 2000-07-24 UptimeMinutes: 37 Total: 37 OS: Windows NT 4.0 build 1381 URL: Comment: crash again with deleting the last message in thread pane and then scrolling in the folder pane. Known bug reported. 7-24 am build. win32. Build: 2000072421 CrashDate: 2000-07-25 UptimeMinutes: 54 Total: 54 OS: Windows 98 4.10 build 67766446 URL: Comment: Opening IMAP "INBOX" after having selected another folder and not waited for action to be finished. Build: 2000072509 CrashDate: 2000-07-26 UptimeMinutes: 267 Total: 267 OS: Windows NT 4.0 build 1381 URL: www.mirc-colors.com Comment: trying to leave the page.
Keywords: topcrash
Fixed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Using july31 commercial m17 builds, linux rh6.0 and mac OS 9.0 Using july29 commercial m17 build NT 4.0 I'm seeing no crash in this situation. These display problems fixed: -- column squishing -- missing scrollbar These display problems still happen, particularly if you scroll: -- blankline(s) at top of thread pane after several deletions -- multiple selections (only sometimes, particularly linux) -- no selection at all -- scrollbar can't get back down to bottom of list without hassle The worst and most noticeable problems are gone. Let me know what we want to do with the lingering stuff.
Added some status summary wording for beta2 watchers. Will most likely close this out and log new/clearer bugs for the remaining display problems. Will do that soon, not marking verified yet since Lisa saw a scroll crash and is investigating whether it's the same as this.
Whiteboard: [nsbeta2+]Fix in hand. Give the word. → [nsbeta2+]Verified worst symptoms/crash 7/31 all platforms.
Laurel - My scroll crash didn't have to do with deleting msgs first, I believe. Log separate bugs for the lingering problems you see with the UI. I'll mark verified.
Status: RESOLVED → VERIFIED
Keywords: relnote2
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.