Audacious UI sluggish. Hangs totally when bound to single cpu core...

D

Dragony

So thats weird. New computer. AMD this time. Updated everything and everything is working correctly, but the UI of Audacious has some strange problem.... but only when a song is playing. No problem when its playing nothing.

When I hit play, the UI becomes very sluggish, but it sounds good, no clicks or pops. But then scrolling the playlist becomes very sluggish. Like its only 3 fps. And here comes the extra weird thing: When I do "cpuset -l 0 -p PID", the UI completely hangs. Nothing works anymore. But the song is still playing. When I do "cpuset -l all -p PID", it instantly works again, sluggishly.

There is something really weird going on. Any idea? Tried GTK and QT version. Both having the same problem.

Installed via "pkg install audacious-gtk3" and also tried "pkg install audacious".

freebsd-version -kru
14.3-RELEASE-p2
14.3-RELEASE-p2
14.3-RELEASE-p2

audacious -v
Audacious 4.5 (unknown build)
 
While audacity can be quite powerful, I've found it to be somewhat lacking in code quality. Many of the delays I've encountered are due to polling of sound channels and waiting for responses in a blocking fashion. This is especially true at startup, and when you activate a particular sound source/sink.

Never mind...it seems you also made the common faux-pah of intermixing audacity and audacious
 
Oh my yeah of course I mean audacious. To my excuse, I searched for the problem with DuckDuckGo before and they gave me many audacity results instead. So they have obviously brainwashed me... ;)

But that doesn't explain that it completely hangs when limited to a single core, does it? Can someone reproduce the problem? Do cpuset -l 0 -p <PID> and see if your UI is still responsible while it's playing something.
 
You must log in or register to reply here.
Back
Top