sdbarker
May 2 2004, 14:13
When using FB2k 0.8.1 release, under WindowsXP SP1, closing foobar only closes the main window. The executeable remains in the process list, consuming resources. This behavior occurs when using File / Close, Alt+F4, the close button in the upper right, and when using StrokeIt to send WM_CLOSE to the application.
-Scott
picmixer
May 2 2004, 14:20
Any chance you have foo_audioscrobbler or any of the recent alphas of foo_ui_columns installed? If so try removing them and see if the problem persists.
I am almost sure it won't.
sdbarker
May 2 2004, 15:21
Nope, neither of those. I have
foo_diskwriter.dll
foo_dsp_extra.dll
foo_input_std.dll
foo_masstag.dll
foo_output_std.dll
foo_read_http.dll
foo_recycle.dll
foo_rgscan.dll
foo_ui_std.dll
foo_vis_bacon.dll
foo_vis_manager.dll
Sorry I forgot to include that in my initial post. I knew I was forgetting something.
What version of foo_vis_bacon do you have installed? Old versions had a bug where they'd deadlock if you tried to close foobar while you had a Winamp visualization going, but I was pretty sure I'd fixed that in the latest version.
sdbarker
May 2 2004, 17:38
minus0.5alpha
Yeah, that was one of the buggy ones. Take a look at
this post to get a fixed version.
sdbarker
May 5 2004, 18:17
Stellar. Thanks for the help.
Sorry for the slow reply. Work / home life has been eating my soul. ;-)
admiraljustin
May 6 2004, 23:17
I have this problem too, minus the vis_bacon though.
I've become acquainted well with
CODE
taskkill /f /fi "IMAGENAME eq foobar2000.exe" /im *
good old taskkill /f

i've had same problem but it was foo_vis_samurize2 or what's the name. new version of samurize uses foo_info_samurize, so it wasn't needed anyway.
may be your case, give it a try
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.