User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:18.104.22.168) Gecko/20100214 Ubuntu/9.10 (karmic) Firefox/3.5.8 Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:22.214.171.124pre) Gecko/20100217 Shredder/3.0.3pre Steps: 1) Open Thunderbird with fresh profile. 2) Set up IMAP account. 3) Select message (I tried a few). 4) Delete, undo, delete, undo, delete, undo Result: Thunderbird exits without any warning Expected action: I should be able to do this until I get sick of it. Further notes: 1) If I wait for all the background activity (moving, deleting and loading) to settle down before each step, the crash does not happen. However, this takes 3-5 seconds each time, so one cannot expect users to wait. 2) For some messages, I cannot undo the delete. That's a possible fix, I guess, but going through the Trash to pull out an accidentally deleted message is not my idea of fun. *goes to wash hands* What happens in the "cannot undo" case is this: 1) The e-mail pops back into the list for half a second. 2) It then disappears. 3) Redo and Undo seems to bring it back. 3) I have been able, by a sequence of Undo and Redo to get 2 copies of the message. 4) The whole thing is mildly unpredictable, although it always happens to a particular message. 5) If I wait for background activity to complete, the bug does not happen. However, I do get a "vanish and reappear" effect when the deletion is undone. Reproducible: Always
Component: Folder and Message Lists → Backend
Product: Thunderbird → MailNews Core
QA Contact: folders-message-lists → backend
Wayne: yes, as I wrote in (2) of "Steps".
can you follow https://wiki.ubuntu.com/MozillaTeam/Bugs#Obtain%20a%20backtrace%20from%20an%20apport%20crash%20report%20%28using%20gdb%29 replace firefox by thunderbird. Would be very nice to have a stack trace.
I can't reproduce with current trunk and there is no stacktrace, so => incomplete Alexey if you can reproduce, please attach stacktrace as a file to the bug
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.