on atom N550 the pavucontrol eats 23% of cpu and X 14% even when input and output are both completely muted. i guess this is just sloppy programming, updating the meters even when nothing is going on. this is effectively a busy-loop burning and would be really nice to fix, please?
on atom N550 the pavucontrol eats 23% of cpu and X 14% even when input and output are both completely muted. i guess this is just sloppy programming, updating the meters even when nothing is going on. this is effectively a busy-loop burning and would be really nice to fix, please?