From: Rick Pasotto <rick@ni...> - 2010-02-03 15:11:32
My system seemed to be running slowly so I fired up htop to see what was
going on. Turns out audacity was using upto 88% of available cpu even
though it wasn't doing any processing and was actually minimized.
audacity version 1.3.10-1 (debian)
I see there's a 1.3.11-1+b1 version in sid. Might that solve the problem?
"...under the Rule of Law...the individual is free to pursue his
personal ends and desires, certain that the powers of government will
not be used deliberately to frustrate his efforts." -- Friedrich Hayek
Rick Pasotto rick@... http://www.niof.net
From: Al Dimond <businessmanprogrammersteve@gm...> - 2010-02-03 16:03:50
On Wednesday 03 February 2010 07:49:04 Rick Pasotto wrote:
> My system seemed to be running slowly so I fired up htop to see
> what was going on. Turns out audacity was using upto 88% of
> available cpu even though it wasn't doing any processing and was
> actually minimized.
This is due to a bug in wxWidgets. We couldn't find a good way to work
around it, and somehow the wx folk still haven't released a version
with the fix in.
Audacity (and any app that uses certain wxWidgets features) will eat
gradually more CPU the longer it sits idle. Fortunately it won't eat
much RAM while doing so. About all you can do is close it when you're
not actively using it. Or, since it's fixed in their SVN you could
build yourself new wxGtk libraries from SVN head on the stable branch.
> audacity version 1.3.10-1 (debian)
> I see there's a 1.3.11-1+b1 version in sid. Might that solve the
Get latest updates about Open Source Projects, Conferences and News.