Closed Bug 210817 Opened 21 years ago Closed 15 years ago

ASSERTION: when deleting selected messages

Categories

(MailNews Core :: Backend, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: bugzilla, Unassigned)

References

Details

if you use the search bar to find some messages and the select them all and
delete them your get:

###!!! ASSERTION: selected indices is not equal to num of msg selected!!!:
'numSelected == selection.GetSize()', file
c:/mozilla/mozilla/mailnews/base/src/nsMsgDBView.cpp, line 993
if you have a folder with 10 messages and type something into the search so that
only 2 messages are shown and highlight these 2 messages and delete them the
debug says:

------
numSelected <2>
GetSize <2>
nsMsgDatabase::Commit(1)
nsMsgDatabase::Commit(0)
numSelected <1>
GetSize <0>
###!!! ASSERTION: selected indices is not equal to num of msg selected!!!:
'numSelected == selection.GetSize()', file
s:/mozilla/mozilla/mailnews/base/src/nsMsgDBView.cpp, line 996
----------

so it seems that the first number (2) is correct. But then suddenly numSelected
says 1. Weird.

Deleting just one message doesn't produce this assertion.
Blocks: 160540
Product: MailNews → Core
Henrik, do you still see this?  I just tried TB1.5 with -console and see no 
such errors, deleting from local folders.

If you're using IMAP, what's the deletion model?
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
Filter on "Nobody_NScomTLD_20080620"
QA Contact: esther → backend
Product: Core → MailNews Core
is assertion still seen in nightly SM or thunderbird?
Tried to reproduce on Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b5pre) Gecko/20090506 SeaMonkey/2.0b1pre, I don't get any assertion.
Neither do I, on a recent debug TB build.

-> WFM.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.