Hello banshee,

We've worked on memory leaks, and added many local autorelease pools so that, as you indicated, relaunching to release memory doesn't help.

20,000 bookmarks is a lot, and I know there is a performance bottleneck which occurs if you have thousands of bookmarks in one folder and start moving them around.  All of the others need to be displaced, and this is slow.  This is probably what you're experiencing.  It's an area that needs some programming work.

If you have such huge folder(s) which you are moving items out of, I think it would help to create, say, ten empty folders, then select swaths of bookmarks and move each swath into one of these empty folders.  The contextual menu item Move to… is handy for this.  Then you should be able to do your actual reorganization work from these folders with much shorter beachballs.

That's not a nice workaround.  If you're not in a hurry, we're going to look at some of these performance issues later this week and see if we can publish an update with better performance.  If you wouldn't mind zipping your .bkmslf document and sending to support@sheepsystems.com, I'd like to test your specific case and make sure we've got you covered.