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 V-2.0 process still running after closing the player (Read 3384 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

foobar2000 V-2.0 process still running after closing the player

Hi there

I'm not sure if this is a bug, or it's just on my machine.

After exiting/closing the app, I can't re-open the player, nor play or add a new file/folder - nothing happens.
Windows 10 Task manager shows that the process is still running (but the player is absolutely closed).
In order to open the app or play/add a new file I must kill its process from task manager.

This issue started to happen since I upgraded to version 2.0, but it doesn't occur always.

I'm using foobar2000 V-2.0 32 bit on Windows, 10 22H2.

Any idea?
Is it a bug ?
Does anyone else experiencing such an issue?

Thanks in advance

Re: foobar2000 V-2.0 process still running after closing the player

Reply #1 –
Sounds like you have a bugged component.

Appendix B of the old help post: https://hydrogenaud.io/index.php/topic,67779.0.html

Running the component troubleshooter isn't a bad idea either.

Re: foobar2000 V-2.0 process still running after closing the player

Reply #2 –
I have the same problem, Win10 FB2x64.
Foobar troubleshooter says DVDA-0.6.1 plugin is the cause.  It never happened in FB1.16 with the same DVDA-0.6.1 plugin.

Re: foobar2000 V-2.0 process still running after closing the player

Reply #3 –
Are you using the following components?
Move to Desk Top Temporarily.

VST 2.x/3.x Adapter (foo_dsp_vst3)
Spider Monkey Panel (foo_spider_monkey_panel)
JScript Panel 3 (foo_jscript_panel3)

Depends on PC performance.
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD620S, SENNHEISER HD 490 Pro Plus, beyerdynamic DT 1990 PRO, HiFiMAN Edition XS, HIFIMAN ANANDA, Bowers & Wilkins P7, FiiO FT5, FiiO FT1 Pro, 水月雨 (MOONDROP) 空鳴 - VOID, SONY WH1000XM5 (made a Upgrade/Balanced Cable by myself)

Re: foobar2000 V-2.0 process still running after closing the player

Reply #4 –
Quote from: Air KEN on
JScript Panel 3 (foo_jscript_panel3)

If you think a given component is problematic, it's customary to report it so the developer might have a chance of fixing it. Thanks. :/

Re: foobar2000 V-2.0 process still running after closing the player

Reply #6 –
I have the same problem.
I only use Foo_input_sacd
 

Re: foobar2000 V-2.0 process still running after closing the player

Reply #7 –
Hi everyone

Thanks for your advice, appreciate that.

@Case:

The troubleshooter gave me these results:

foobar2000 troubleshooter
The following components found on your system are known to be problematic and should be either uninstalled or updated to their latest versions:

foo_uie_vis_peakmeter_spectrum.dll : Peakmeter Spectrum Visualisation 0.2.0.0 beta
Reason: Repeated crash reports.

foo_httpcontrol.dll : HTTP Control 0.97.14-fb2kc
Reason: Repeated crash reports.
Download the latest version...

foo_bpm.dll : BPM Analyser 0.2.4.6
Reason: Repeated crash reports.
Download the latest version...

foo_discogs.dll : Discogs Tagger 2.23
Reason: Repeated crash reports.
Download the latest version...

Now the thing is that the last 3 components (foo_httpcontrol, foo_bpm and foo_discogs) are already the latest version exist (or I may missing something..).

The first one foo_uie_vis_peakmeter_spectrum works fine and I never had any problem with it.

About this: https://www.foobar2000.org/components/view/foo_crash.

I'm sorry but didn't get it, shall I install this component and run it??  Thanks


@wojak

I'm not using  DVDA-0.6.1


@Air KEN:

I'm not using any of these components:

VST 2.x/3.x Adapter (foo_dsp_vst3)
Spider Monkey Panel (foo_spider_monkey_panel)
JScript Panel 3 (foo_jscript_panel3)


@seomanakasimon

I'm using foo_input_sacd as well, but I don't know if this is the reason..


I'll keep monitoring this issue, and I hope the next update will fix it.

Thanks a lot guys, you are really great!

Re: foobar2000 V-2.0 process still running after closing the player

Reply #8 –
Quote from: yuzzi on
The troubleshooter gave me these results:
[...]
Now the thing is that the last 3 components (foo_httpcontrol, foo_bpm and foo_discogs) are already the latest version exist (or I may missing something..).
I trust you are on the latest versions. The troubleshooter doesn't know what is out there. It hopes there is a newer release that fixes the bugs.

Quote from: yuzzi on
About this: https://www.foobar2000.org/components/view/foo_crash.

I'm sorry but didn't get it, shall I install this component and run it??
Yes. It is a debugging tool meant to help find the cause of the hanging.

Quote from: yuzzi on
I'll keep monitoring this issue, and I hope the next update will fix it.
No update will change anything unless the cause is found. Personally I'm 100% positive the cause is in a third party component, so a future foobar2000 update can at best work around the bug unless the author fixes it. But if no one bothers to even check the cause of the hang, nothing will get fixed.

PS: by the sound of the components you have installed, foo_httpcontrol.dll seems like something that would create services that could prevent clean shutdown when there are problems.

Re: foobar2000 V-2.0 process still running after closing the player

Reply #9 –
Quote from: Case on
PS: by the sound of the components you have installed, foo_httpcontrol.dll seems like something that would create services that could prevent clean shutdown when there are problems.
I have been fiddling with httpcontrol, its removed now and i haven't had a 'sticky' foorbar recently.
So you might be on to something

Re: foobar2000 V-2.0 process still running after closing the player

Reply #10 –
Hi,
I contacted the author od DVDA componet and he kindly made a new version which for now is not treated as a cause of crach by foobar (I do not know if it was a cause at all)...The same person wrote SACD plugin so if some of you think that that component may be the cause please contact him and he probably will also update the SACD plugin.
As for other components...at least httpcontrol has a few newer versions (https://bitbucket.org/oblikoamorale/foo_httpcontrol/downloads/) with 26 being the most actual.

VST adapter is Peters..so if someone feels it is a cause....it will probably be fixed very soon....but that someone has to inform Peter about this situation.

Re: foobar2000 V-2.0 process still running after closing the player

Reply #11 –
Similar problem. It freezes now and then when I close foobar with X. Plugins are ok. I've noticed it happens more when the PC is a little busy. (HDD access)

Re: foobar2000 V-2.0 process still running after closing the player

Reply #12 –
Same here. Just upgraded the SACD component to 1.5.4 because of the reply I saw here.

Current report:
foo_uie_vis_channel_spectrum.dll : Channel Spectrum panel 0.17.2
Reason: Repeated crash reports, division by zero bug.
Download the latest version...

foo_uie_vis_peakmeter_spectrum.dll : Peakmeter Spectrum Visualisation 0.2.0.0 beta
Reason: Repeated crash reports.

foo_uie_elplaylist.dll : ELPlaylist 0.6.9.1.2(beta)
Reason: Repeated crash reports.
Download the latest version...

foo_uie_lyrics3.dll : Lyric Show Panel 3 0.5
Reason: Repeated crash reports.

foo_input_dvda.dll : DVD-Audio Decoder 0.6.1
Reason: Repeated crash reports.

Re: foobar2000 V-2.0 process still running after closing the player

Reply #13 –
Please remove them.
SHURE SRH1840, SENNHEISER HD660S2, SENNHEISER HD620S, SENNHEISER HD 490 Pro Plus, beyerdynamic DT 1990 PRO, HiFiMAN Edition XS, HIFIMAN ANANDA, Bowers & Wilkins P7, FiiO FT5, FiiO FT1 Pro, 水月雨 (MOONDROP) 空鳴 - VOID, SONY WH1000XM5 (made a Upgrade/Balanced Cable by myself)
 

Re: foobar2000 V-2.0 process still running after closing the player

Reply #14 –
So many "me too" replies and not a single one of you manages to install the foo_crash component? It should automate diagnosing the issue by providing a super useful crash dump when the freeze happens.
Alternatively please use Process Explorer and check the treads still running, as pointed in the linked help post. It should quite easily at least name the component that is causing it.

Re: foobar2000 V-2.0 process still running after closing the player

Reply #15 –
Quote from: Case on
So many "me too" replies and not a single one of you manages to install the foo_crash component?

People on this forum not reading? Imagine my shock.

Re: foobar2000 V-2.0 process still running after closing the player

Reply #16 –
Please update!

foo_httpcontrol: Fix possible lockup on foobar2000 shutdown; 0.97.27 released

Re: foobar2000 V-2.0 process still running after closing the player

Reply #17 –
Hi everyone

Sooooooooooooooooooo

Quote from: wojak on

As for other components...at least httpcontrol has a few newer versions (https://bitbucket.org/oblikoamorale/foo_httpcontrol/downloads/) with 26 being the most actual.


&

Quote from: BBSRom on
Please update!

foo_httpcontrol: Fix possible lockup on foobar2000 shutdown; 0.97.27 released


Thanks for this !
I Just updated httpcontrol to 0.97.27, and BOOOOOM!!!!  it seems to solved the problem :)

I can see the foobar2000 process disappear from Task Manager right after I exit the player.


As for this:

Quote from: Case on
So many "me too" replies and not a single one of you manages to install the foo_crash component? It should automate diagnosing the issue by providing a super useful crash dump when the freeze happens.
Alternatively please use Process Explorer and check the treads still running, as pointed in the linked help post. It should quite easily at least name the component that is causing it.


You are absolutely right, don't know why I didn't do so, I'll install it.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I still have few questions please:

1. Why when I was looking for components' updates, the Get updates returns: "No updates are available at this time" ?

2. Why the online troubleshooter ask to "Download the latest version" of: foo_bpm.dll : BPM Analyser 0.2.4.6 and foo_discogs.dll : Discogs Tagger 2.23?

I couldn't find any newer version for both of them.

3. foo_uie_vis_peakmeter_spectrum.dll : Peakmeter Spectrum Visualisation 0.2.0.0 beta - is working just fine with my player (screenshot) so why the online troubleshooter shows: Reason: Repeated crash reports.


Thanks again to all of you, I really appreciate your will to assist and your time.
And good luck for all the others that experiencing similar or other issues, you are at the right place :)

Best Regards

🙏


Re: foobar2000 V-2.0 process still running after closing the player

Reply #18 –
Quote from: yuzzi on
1. Why when I was looking for components' updates, the Get updates returns: "No updates are available at this time" ?
The update checker can only check the official component repository: https://www.foobar2000.org/components.

Quote from: yuzzi on
2. Why the online troubleshooter ask to "Download the latest version" of: foo_bpm.dll : BPM Analyser 0.2.4.6 and foo_discogs.dll : Discogs Tagger 2.23?
I thought I already answered here: https://hydrogenaud.io/index.php/topic,124144.msg1027095.html#msg1027095.
The Troubleshooter does not know what versions are out there. It always asks to get an update if it knows the version you are on is buggy and crashes a lot. It could of course be better but if it was kept up-to-date on all new component versions even outside component repository, it would require constant manual labor. The suggestion to get an update is also kinder than asking you to uninstall the component.

Quote from: yuzzi on
3. foo_uie_vis_peakmeter_spectrum.dll : Peakmeter Spectrum Visualisation 0.2.0.0 beta - is working just fine with my player (screenshot) so why the online troubleshooter shows: Reason: Repeated crash reports.
The Troubleshooter analysis is based on what is seen happening around the globe. That particular component has crashed a lot on several different setups and thus has gotten on the warning list.