Wow.  My BookMacster has been chewing on your log files for the last 20 minutes, trying to delete old entries, using 100% of CPU indeed.  This is not normal behavior.

From your logs, I also see that a BookMacster-Worker crashed earlier today while it was doing the same thing.

We'll figure out what's going on and put in a branch to gracefully handle corrupt log files in the next version.  In the meantime, I would say that you can probably fix this by deleting your Logs file as it is apparently quite corrupt.

• Force Quit Agents Workers, if any, as described in my previous message.
• Quit BookMacster.
• In Finder, navigate to Home ▸ Library ▸ Application Support ▸ BookMacster.
• Trash the file named Logs.sql.

Regarding your Agents settings, you can either set them back to Simple Agents, which will sync whenever changes are detected, or if you truly want the sync done only manually or weekly, leave everything unchecked or else use the Agents ▸ Advanced to schedule them once a week as described in my previous message.  Even though the CPU burden of syncing whenever changes are detected is small, if you don't value it, BookMacster's advanced settings allow you to customize.

?ô wrote on Jul 1^st, 2011 at 8:04pm:
We use a different word.  The background operations are triggered by a BookMacster Agent and performed by a BookMacster-Worker.  To turn them off, launch BookMacster, click in the menu BookMacster ▸ Active Agents.  Select one and click Edit, then change the view to Simple if necessary, finally un-check all the boxes.

By default, Agents sync whenever bookmarks changes are detected, although they are throttled to occur no more often than every 5 minutes.  You can reduce the operation of Agents sync only once per week.  To do that,

• In Simple Agents, check the two boxes Import Changes from Clients and Export Results to Clients.
• Click the tab Advanced.
• In the Triggers table, delete all triggers except one.
• Click the remaining trigger and in the popup menu select Scheduled.
• In the next two columns, enter day and time.


?ô wrote on Jul 1^st, 2011 at 8:04pm:
A BookMacster-Worker process typically runs for a few seconds and then disappears; more than a few seconds if you have an old Mac, many Clients, or thousands of bookmarks.  During these seconds, it will typically use all the CPU that the system will give it, which is 100% if nothing else is going on.

But let's make sure that nothing bad is happening.  In BookMacster, click the menu BookMacster and look at the Force Quit Agents' Workers item.  This menu item is our emergency cutoff switch.  Normally it is disabled ("grayed out"), indicating that no BookMacster-Workers are currently running.  If a Worker got stuck on, you can use this menu item to force quit it.

I'd like to look at BookMacster's Logs to see if you have too much BookMacster-Worker activity.  To send us your logs, in BookMacster click in the menu Help ▸ Trouble Zipper.  When answering the questions, it might be good to Include bookmarks and Bookmarkshelf Documents so we can see if there's anything in there that's causing BookMacster-Worker to run for a long time.  I recently tested BookMacster with the data of a user that had 488,000 bookmarks.  Thanks to performance improvements in recent versions, BookMacster did slog through them, but it took a while.  (Oh, they were almost all duplicates from his long history of telling browsers to migrate bookmarks.  He eliminated them using BookMacster's Delete All Duplicates.)

?ô wrote on Jul 1^st, 2011 at 8:04pm:

Thank you; it's already been noticed and fixed for the next version.