Hi, i've found why audacious takes 100% CPU, doesn't respond, and needs a "kill", when the last item of the playlist is not playable (access denied, not an audio file, maybe other reasons). Each loop calls many open() syscalls which heavy in some cases. The future 1.3 branch is fixed upstream but our 1.2.2 ebuild needs a fix. i propose two patches, the first being a backport from upstream 1.3-alpha (but now fixed, it was initially incorrect), and the second is an adaptation from the first one, which will catch all potential pathological cases imho.
Created attachment 105707 [details, diff] Upstream backport
Created attachment 105709 [details, diff] another proposal
Finally upstream has chosen to switch to the second patch (with "for(penalty...)" )
For which audacious did you report ? if your patch have been emrged, is new ebuild available ? if yes, please close !
1.3 solves this issue. For the most part, this can be closed.
yes sure, upstream has fixed it and incorporated my proposal in 1.3-alpha-something, so in media-sound/audacious-1.3.0-rc2 which is not in the stable tree yet, but maybe on its way.
