Joachim is right, the process is checking if the volume has changed
every microsecond, this is known to cause problems in some setups.
if you just change that value to a more reasonable one, it should be
fine. usleep(1) should work fine.
it is right that this is not the best way to do t
Hi,
Am Sonntag, den 19.10.2008, 22:20 +0200 schrieb Moritz Molle:
> Joachim Breitner wrote:
> > Am Sonntag, den 19.10.2008, 02:05 +0200 schrieb Moritz Molle:
> >>
> >> If you configure osdsh to show audio-mixer changes (osdctl -m 1), it eats
> >> up
> >> 100% of cpu. This is because in mixerwatch
Hi,
Am Sonntag, den 19.10.2008, 02:05 +0200 schrieb Moritz Molle:
> Package: osdsh
> Version: 0.7.0-9
> Severity: important
>
>
> If you configure osdsh to show audio-mixer changes (osdctl -m 1), it eats up
> 100% of cpu. This is because in mixerwatch.c there is a line which looks
> like so:
>
Package: osdsh
Version: 0.7.0-9
Severity: important
If you configure osdsh to show audio-mixer changes (osdctl -m 1), it eats up
100% of cpu. This is because in mixerwatch.c there is a line which looks
like so:
usleep(1);
This is wrong, because this doesn't really sleep at all. It should be sle
4 matches
Mail list logo
