Allow me to provide some background information. I finally decided to install Windows x64 on my AMD last week since it seemed that most of the little issues have been ironed out. I went with a fresh install of Foobar and downloaded the usual plugins and I started to customize to my heart’s content. Everything worked fine like usual. Yesterday I finally decided to enable the database. I checked the box and entered in my folders for it to manage. I did not click scan however. Later that day, after closing my Foobar and reopening it, everything slowed way down as it was trying to open. I slowly but surely managed to open my task manger to try and see what was going on. Foobar was taking up 99% of my CPU resources. It didn’t seem to be frozen or anything like that though because the statistics would continue to refresh. Foobar’s utilization would drop to 98 or 97 and then go back to 99 and all the other programs would sometimes increase or decrease like usual. So it wasn’t as if my system or Foobar had frozen. I figured that since I hadn’t clicked scan when I enabled the database, it must be scanning the folders now. It was getting late so I figured I would just let it run overnight and it would be fine in the morning.

This morning it was still using up 97-99% of my CPU and I couldn’t get any other work done. So I just ended the process and everything went back to normal. I figured maybe my database got messed up, since that had been the only change I made to Foobar since the last time I opened it. I went into my foobar2000 folder and changed my database.foo to database.foo.bak and then tried to open Foobar again. Worked like a charm, no problems whatsoever. I figured my database must of gotten corrupt or something. So I go into the preferences and disable the database. I then close and reopen Foobar. I have the exact same problem as before. Foobar takes up all my CPU, but again it doesn’t appear to be frozen. I am slowly able to end the process and my system goes back to normal.

I try closing and reopening a few more time, restart a few times, the usual stuff…still nothing. Foobar just refuses to open and it takes my processor with it. I am now at a loss for what to do short of reinstalling Foobar.

Any help would of course be appreciated.
Thanks.

I have the same problem on one machine (but not on another similar one).

After I close FB, if I launch the task manager I can still see the Foobar2000.exe in the process list.
In my case it is probably due to a Samurize plugin for FB.

To make FB open again I have to kill the process first.

If you find this kind of behaviour, try with a FB clean install with no additional plugins then, if it works, add one plugin and then try open/close/open etc and go on like this.

I would enable the database as the only preferences tweak while doing these tests.