Comment 24 for bug 443121

Jeremy Nickurak wrote:
> So what exactly is the work around? And why is this marked "Fixed" if
> people are still affected by it?

The workaround right now, if it's really crippling, is to disable the
Bindwood extension. It was marked Fixed because the initial bug was
about the unresponsiveness and bloat caused by the livemarks.

> I see people talking about removing a "Live Bookmarks" folder, but I
> don't see that anywhere. And I see stuff about removing couchdb stuff,
> but I don't know anything about that. A detailed explaination of what to
> do would help those who show up here because they're affected by this.

> Zachery: This still seems like a bad solution. Why isn't this just done
> in the background, so that firefox remains responsive while the bookmark
> sync is happening?

The simplest explanation is that I didn't want to dive into dealing with
threads until I saw a need. In retrospect, it was a naive decision.

I agree with you: there shouldn't be any responsiveness penalty for the
user, regardless of bookmarks corpus size. So I'm now exploring
Firefox's thread manager to make all bookmarks collection and network
operations happen on a background thread.

Thanks,

Zac