Closed
Bug 384752
Opened 17 years ago
Closed 17 years ago
onItem* notifications are dispatched for closed containers (was: lots of assertions ("Removing item we don't have" and "Invalid index for item adding") when I reload a live bookmark and the bookmark organizer window is open)
Categories
(Firefox :: Bookmarks & History, defect, P2)
Firefox
Bookmarks & History
Tracking
()
RESOLVED
FIXED
Firefox 3 beta1
People
(Reporter: moco, Assigned: asaf)
References
Details
Attachments
(1 file)
6.38 KB,
patch
|
dietrich
:
review+
mconnor
:
approval1.9+
|
Details | Diff | Splinter Review |
lots of assertions when I reload a live bookmark and the bookmark organizer window is open: I'm getting a lot of these: ###!!! ASSERTION: Removing item we don't have: 'Not Reached', file c:/builds/tru nk/mozilla/toolkit/components/places/src/nsNavHistoryResult.cpp, line 3110 followed by a lot of these: ###!!! ASSERTION: Invalid index for item adding: greater than count: 'Not Reache d', file c:/builds/trunk/mozilla/toolkit/components/places/src/nsNavHistoryResul t.cpp, line 3038 steps to reproduce: 1) create a new profile 2) open the bm manager window 3) right click on the "latest headlines" rss feed and do "reload live bookmark" I'm using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a6pre) Gecko/20070615 Minefield/3.0a6pre [note, I see this with and without the fix for bug #383572]
Reporter | ||
Updated•17 years ago
|
Summary: lots of assertions when I reload a live bookmark and the bookmark organizer window is open → lots of assertions ("Removing item we don't have" and "Invalid index for item adding") when I reload a live bookmark and the bookmark organizer window is open
Assignee | ||
Comment 1•17 years ago
|
||
Morphing a bit, this is also the cause for various random front-end assertions.
Summary: lots of assertions ("Removing item we don't have" and "Invalid index for item adding") when I reload a live bookmark and the bookmark organizer window is open → onItem* notifications are dispatched for closed containers (was: lots of assertions ("Removing item we don't have" and "Invalid index for item adding") when I reload a live bookmark and the bookmark organizer window is open)
Comment 2•17 years ago
|
||
http://lxr.mozilla.org/mozilla/source/toolkit/components/places/src/nsNavHistoryResult.cpp#1187 see also https://bugzilla.mozilla.org/show_bug.cgi?id=386243#c2
Assignee | ||
Comment 3•17 years ago
|
||
So, to summarize: 1. The contents of a bm folder is built once containerOpen = true is set on the container. 2. The contents are _not_ destroyed when the container is closed, unlike complex queries, thus the bookmark observers are still set as well. This is all by design since incremental update for simple folder result nodes is cheap. 1. Only one view->Item...() caller in nsNavHistoryFolderResultNode has that in mind.
Assignee: nobody → mano
Target Milestone: --- → Firefox 3 beta1
Updated•17 years ago
|
Target Milestone: Firefox 3 M7 → Firefox 3 M8
Updated•17 years ago
|
Target Milestone: Firefox 3 M8 → Firefox 3 M9
Assignee | ||
Updated•17 years ago
|
Flags: blocking-firefox3?
Assignee | ||
Comment 4•17 years ago
|
||
Attachment #281078 -
Flags: review?(dietrich)
Comment 5•17 years ago
|
||
Comment on attachment 281078 [details] [diff] [review] patch r=me, thanks
Attachment #281078 -
Flags: review?(dietrich) → review+
Assignee | ||
Updated•17 years ago
|
Attachment #281078 -
Flags: approval1.9?
Updated•17 years ago
|
Attachment #281078 -
Flags: approval1.9? → approval1.9+
Assignee | ||
Comment 6•17 years ago
|
||
mozilla/toolkit/components/places/src/nsNavHistoryResult.cpp 1.114
Status: NEW → RESOLVED
Closed: 17 years ago
OS: Windows XP → All
Priority: -- → P2
Hardware: PC → All
Resolution: --- → FIXED
Updated•17 years ago
|
Flags: blocking-firefox3? → blocking-firefox3+
Comment 7•15 years ago
|
||
Bug 451915 - move Firefox/Places bugs to Firefox/Bookmarks and History. Remove all bugspam from this move by filtering for the string "places-to-b-and-h". In Thunderbird 3.0b, you do that as follows: Tools | Message Filters Make sure the correct account is selected. Click "New" Conditions: Body contains places-to-b-and-h Change the action to "Delete Message". Select "Manually Run" from the dropdown at the top. Click OK. Select the filter in the list, make sure "Inbox" is selected at the bottom, and click "Run Now". This should delete all the bugspam. You can then delete the filter. Gerv
Component: Places → Bookmarks & History
QA Contact: places → bookmarks
You need to log in
before you can comment on or make changes to this bug.
Description
•