https://bugs.winehq.org/show_bug.cgi?id=47094
Bug ID: 47094 Summary: Foobar2000 memory leak Product: Wine Version: 4.7 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: just4steam778@gmail.com Distribution: ---
Created attachment 64291 --> https://bugs.winehq.org/attachment.cgi?id=64291 Terminal output
I have an issue with foobar2000 taking up 15-25% of CPU power and 0.4-1GB of RAM and eventually crashing. This happens soon after launch even when it's idle as a fresh installation. I've also tried installing it in a 32-bit Windows XP prefix.
I'm running foobar2000 1.4.3 on Arch Linux.
https://bugs.winehq.org/show_bug.cgi?id=47094
Daniil Zhilin just4steam778@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |just4steam778@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=47094
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 URL| |https://www.foobar2000.org/ | |download Keywords| |download Status|UNCONFIRMED |NEW
--- Comment #1 from Austin English austinenglish@gmail.com --- I see high CPU usage, not so much with memory. Doesn't crash for me though. How long does it take to crash for you?
https://bugs.winehq.org/show_bug.cgi?id=47094
Gothox mondaybreak@mail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mondaybreak@mail.com
--- Comment #2 from Gothox mondaybreak@mail.com --- I've had the same issue but with a much older version of F2K where I had imported an old(ish) theme and components, extreme CPU and RAM usage but no crashes. After doing a clean install and updated wine this problem was gone.
So I just checked and in idle F2k uses absolutely 0% CPU and between 40 and 60 MB RAM, in use the CPU doesn't rise above 15% and the RAM stay relatively similar even after long periods of use. This is on Linux Mint 19.1 and F2K 1.4.3.
My first guess would be that it might be some component or older settings imported into Foobar that causes this but since you've this problem on a fresh install I haven't any idea where the problem is.
One thing you might try is checking F2k's build in console for possible errors right after you launch it. Lets hope that shines some light on the situation.
I also just noticed that F2K 1.4.4 beta has dropped, while I don't think this will resolve the problem, cant hurt to try to update.
https://bugs.winehq.org/show_bug.cgi?id=47094
Daniil Zhilin just4steam778@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NOTOURBUG
--- Comment #3 from Daniil Zhilin just4steam778@gmail.com --- It turned out I just needed to remove the default music folder from the media library settings. Foobar2000 was scanning my whole home directory. I suspected that that setting might be related but forgot to check it. Thanks for the help!
https://bugs.winehq.org/show_bug.cgi?id=47094
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTOURBUG |INVALID
--- Comment #4 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Daniil Zhilin from comment #3)
It turned out I just needed to remove the default music folder from the media library settings. Foobar2000 was scanning my whole home directory. I suspected that that setting might be related but forgot to check it. Thanks for the help!
Application bugs are generally resolved as INVALID. If you change your mind and think there is some Wine bug involved here after all, please reopen this bug report.
https://bugs.winehq.org/show_bug.cgi?id=47094
Alistair Leslie-Hughes leslie_alistair@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Alistair Leslie-Hughes leslie_alistair@hotmail.com --- Closing Invalid.