Update: The Audacious code does appear to be the problem. Specifically, this:
Code: Select all
${if_match "${audacious_status}" == "Playing"}\
${voffset 3}${color orange}${font :size=8}♫ ${voffset 2}NOW PLAYING:${color} ${voffset -2}$stippled_hr
${font DejaVu Sans Mono:size=7}${exec audtool --current-song | fold -sw 30}${font}\
${endif}${voffset 5}
I kept an eye on it over the course of about 5 days and it got up to 30% CPU usage with every Conky tick (it should stay around 1-2%). The memory usage also increased from 0.1% to 0.3% (although negligable, it did increase, when it otherwise shouldn't increase at all from 0.1%).
All I can think of is that there must be something wrong with their Conky/Audacious API. This implementation is a change from my original code which called an external shell script which obtained the song info (included in an earlier post in this thread). I figured this implementation would be more efficient than the other since it doesn't call an external script, but this code still has the same CPU and memory usage problem.
I might look into restarting Conky upon every login, after all, since I do like having Conky display the currently playing Audacious song title. Unless you guys have any other ideas or suggestions?