Anton,

Thanks for taking the time to file a bug. We've added some diagnostic
debugging that can be enabled if FF is run with BINDWOOD_DEBUG in the
process' environment. The easiest way is to run from the terminal (like
you tried):

  $ BINDWOOD_DEBUG=1 firefox &

This will output a lot of debugging messages to the error console. The
default FF error console only allows you to copy one message at a time,
so you could install the Console2 extension ( https://addons.mozilla.org
/en-US/firefox/addon/1815 ) to enable copying multiple lines.

Bindwood iterates over all your bookmarks, pushing each to your desktop
couchdb (after first checking that it's not already present in the db).
During testing and development, it's likely that we didn't provide our
own instances with enough bookmark data to really stress test the setup.
Off hand, do you have an idea of the number of bookmarks you have?

In the future, Bindwood will do a much better job after the first run,
of keeping its network traffic to a bare minimum. As it stands now, it's
a little too chatty.

** Changed in: bindwood (Ubuntu)
     Assignee: (unassigned) => Zachery Bir (urbanape)

** Changed in: bindwood (Ubuntu)
       Status: New => Confirmed

** Also affects: bindwood
   Importance: Undecided
       Status: New

** Changed in: bindwood
       Status: New => Triaged

-- 
With Bindwood installed, Firefox is completely unresponsive
https://bugs.launchpad.net/bugs/443121
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to