393611 - extra "Live Bookmark Loading..." menu items at the top of my live bookmarks menu

Status: RESOLVED DUPLICATE of bug 392984

(Firefox :: Bookmarks & History, defect)

Description

[(not reading, please use [e-mail] instead)]

extra "Live Bookmark Loading..." menu items at the top of my live bookmarks menu

first I had just one, but now I have two.  (on restarting they go away, and they are not visible in the bookmark organizer)

note, this was from a livemark on my personal toolbar folder.

fwiw, manually reloading the live bookmark from the context menu doesn't seem to reproduce it.

let me attach screen shots.

I'm using:  Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a8pre) Gecko/2007082222 Minefield/3.0a8pre

Comment 1

[(not reading, please use [e-mail] instead)]

Attachment: screen shot 1

Comment 2

[(not reading, please use [e-mail] instead)]

Attachment: screen shot 2

Comment 3

[Phil Ringnalda (:philor)]

And no sign of a bug 392984 "failed to load" anywhere? Still likely to be a bug 386603 regression, even if it's not that one.

Comment 4

[(not reading, please use [e-mail] instead)]

phil, thanks for the info about bug #392984 and bug #386603.  I think you are on to something.

from my error console:

Error: this._processor has no properties
Source File: file:///c:/builds/trunk/mozilla/ff-debug/dist/bin/components/nsLivemarkService.js
Line: 927

Error: [Exception... "'Failure' when calling method: [nsINavHistoryBatchCallback::runBatched]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: file:///c:/builds/trunk/mozilla/ff-debug/dist/bin/components/nsLivemarkService.js :: LLL_handleResult :: line 898"  data: no]
Source File: file:///c:/builds/trunk/mozilla/ff-debug/dist/bin/components/nsLivemarkService.js
Line: 898

Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsINavBookmarksService.runInBatchMode]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: file:///c:/builds/trunk/mozilla/ff-debug/dist/bin/components/nsLivemarkService.js :: LLL_handleResult :: line 898"  data: no]
Source File: file:///c:/builds/trunk/mozilla/ff-debug/dist/bin/components/nsLivemarkService.js
Line: 898


Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsINavBookmarksService.runInBatchMode]"  nsresult: "0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame :: file:///c:/builds/trunk/mozilla/ff-debug/dist/bin/components/nsLivemarkService.js :: LLL_handleResult :: line 898"  data: no]
Source File: file:///c:/builds/trunk/mozilla/ff-debug/dist/bin/components/nsLivemarkService.js
Line: 898

Error: not well-formed
Source File: http://feedhouse.mozillazine.org/rss20.xml
Line: 555, Column: 39
Source Code:
 <title>Vladimir Vukicevic: Wow, AT&T.  Just, wow.</title>

Error: this._processor has no properties
Source File: file:///c:/builds/trunk/mozilla/ff-debug/dist/bin/components/nsLivemarkService.js
Line: 927

That matches up with bug #392984, but that is for http://feedhouse.mozillazine.org/rss20.xml, not planet.mozilla.org/atom.xml

Note, firefox has a problem with feedhouse.mozillazine.org/rss20.xml, because of <title>Vladimir Vukicevic: Wow, AT&T.  Just, wow.</title>

(should be AT&ampT).

What to do next:

1) log a bug on firefox about handling feedhouse.mozillazine.org/rss20.xml (if one doesn't exist)
2) contact mozillazine about feedhouse.mozillazine.org/rss20.xml
3) look into bug #392984
4) look into this bug, because the rss feed is not failing.

Comment 5

[Phil Ringnalda (:philor)]

(In reply to comment #4)
> 1) log a bug on firefox about handling feedhouse.mozillazine.org/rss20.xml (if
> one doesn't exist)

A vast number exist, including ones on that exact feed, typically resolved as invalid. The parser we're now using could provide you with the livemarks up to the point of the fatal error (there's currently a comment where the whole feed is thrown on the floor, talking about it being a matter of policy inherited from the 2.0 parser to say that one bad item spoils the whole bunch), though you'll need to figure out a string that could be inserted after the last rescued item to explain in two words "XML well-formedness errors are fatal, and Tim Bray says this feed was generated by a bozo." Or, you could grease up the slippery slope, and decide that RSS isn't XML, it's a stream of bytes which can sometimes be converted into XML by replacing ampersands with entities, and entities with characters, and characters with characters in *this* charset based on a random guess at what *that* charset was, and, and, and..., and try to compete with the other feed readers, which are able to parse it because they spend the bulk of their development time working on turning streams of bytes into XML.

Not that I'm saying this is a hot-button issue or anything.

Comment 6

[Thomas Goldstein]

For what it's worth, I now have 4 "Live Bookmark loading..."lines in one of my RSS bookmarks. A few of which I triggered manually, and at least one of them appeared automatically. It's probably worth noting that the buggy RSS is for my.opera.com, which had technical difficulties earlier today (trying to load a page would tell you they're experiencing problems and that they'd be back soon).
Restarting Minefield doesn't help, the Live Bookmark loading lines all stay.

Screen: http://stifu.free.fr/pics/temp/fxrssbug.png

Comment 8

[Richard Goforth]

Attachment: Live Book Mark Failed to load continues to show up

Comment 9

[Phil Ringnalda (:philor)]

Not having a load failed item was not, it turns out, a sign of success - there are multiple paths to failure, and the only one that got the item was a successful load of a not-well-formed feed. Actual failures to load that happened before that wouldn't get a load-failed, would always leave the loading item behind, and if you were particularly unlucky would leave the livemark locked so it wouldn't refresh again until you restarted. That should all be fixed from bug 392984.

Comment 10

[Gervase Markham [:gerv]]

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