Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: foobar2000.exe doesn't close (Read 1212 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foobar2000.exe doesn't close

For several months I have a constant issue: when I close the program the process stays running, and when I try to open it again it creates more processes. The only way to launch the program is to kill the first hanged process

X

Even if I try to update the program, the updater couldn't kill the process

X

Windows 11 X64, UAC is diabled. I keep using the most recent beta version of 32-bit foobar. The installation and roaming folder remains the same for a decade, no fresh re-install (I don't want to lose my presise tunings).

The program and roaming folders are here: https://dropmefiles.com/v5lTC

Re: foobar2000.exe doesn't close

Reply #1 –
I couldn't replicate the hang at least so far. Try following most of the deadlock debugging steps from https://hydrogenaud.io/index.php/topic,67779.0.html. Taking the stack dumps will probabaly not be helpful. If you are lucky the Threads view will list a component by name name that causes the issue.

If we aren't that lucky you can create a memory dump of foobar2000.exe process with Task Manager. The option can be found in the right click context menu. This at least used to require the use of 32-bit Task Manager to create a usable dump, but let's see if it now works with the default Task Manager.
If you post the memory dump Peter can analyze if and hopefully see what causes the hang.

Re: foobar2000.exe doesn't close

Reply #2 –
Here's the information about the first instance of foobar2000.exe that hanged after closing, takes some cpu, and prevents running other instances;

X

I've noticed it shows new information every time I hit "refresh". That's is the stack trace of only the first thread! Let me know if I have to make it for all the threads:
Spoiler (click to show/hide)

Here's the dump taken with taskmgr from the syswow64 folder:

https://dropmefiles.com/nH5ZH

As for the second instance, when the first is being hanged up, the threads look like this:

X

Spoiler (click to show/hide)

So, it's the DirectShow plugin? Is it safe to remove this guy?

Re: foobar2000.exe doesn't close

Reply #3 –
The foo_input_ds component definitely seems to be the cause of the hang. It is very safe to remove. It has been dead and abandoned for nearly two decades.
The second foobar2000 instance is stuck because it's trying to communicate with the bugged instance. So the extra stuck processes are normal. Memory dump shouldn't be needed as the stuck instance didn't implicate an issue with the player core.

Not related to the hang, so feel free to ignore, but I see you have quite a few older and abandoned components installed. For example the original Dynamic Range Meter is one of the crashiest components in existence according to crash logger. If you have crashes or just want to do maintenance, you can find newer versions to some of the components. For example foo_dr_meter is a new custom implementation of Dynamic Range Meter. And I'll link this foo_dsp_resampler too as it's based on latest version but combines the features of _mod and _mod2 into one without breaking any services that depend on "SoX resampler" having its original name. But that's enough with unwanted suggestions.

Re: foobar2000.exe doesn't close

Reply #4 –
If you really use foo_input_ds to play something, you can use foo_input_ffmpeg instead.

Re: foobar2000.exe doesn't close

Reply #5 –
Awesome! I removed the foo_input_ds module and replaced the ones you mentioned. Now it works like a charm! Thanks!!

There will be another issue about resizing the window after any update, but I'll make another post when it happens.