Audacity uses 100% CPU on opening any file dialog
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
audacity (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: audacity
In Hardy, when I try to save a project or export a file in Audacity (1.3.4-1.1ubuntu1), I get a file dialog with somewhat abridged content (empty where the file listing should be, no directory selector header, etc) and my CPU jumps to 100% of one core. It appears that Xorg (1:7.3+
Steps to reproduce (some of which may not be strictly necessary but this is what I did):
1. Open Audacity, navigate to the Preferences dialog and turn off the "play while recording" checkbox.
2. Open a mixer such as kmix and set your capture options as needed to record a known sound source.
3. Use Audacity to record about 4 minutes from your chosen source.
4. Trim a couple of seconds off each end of the recording.
5. Click on File -> Export... Change the filetype to OGG and change the "Options" to set the quality to 10.
6. Try to navigate to the "Filesystem" via the link on the left of the dialog.
Somewhere around step 5 is when I noticed my CPU being rather heavy. By that point, my pointer had changed to the "busy-wait" spinning icon. I can enter a (path and) filename at the top, but clicking "Save" does nothing. If I hit Escape at this point, the dialog closes, but the CPU remains pegged at 100% of the one core. It stays there until I kill Audacity (though I didn't try to "close" it, I got frustrated and killed it from the command line).
What should happen:
The program should default to the user's home directory, and let me enter my details and save the file or project out. :-)
Changed in audacity (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
The 8.04 Hardy Heron release seems to have a problem with Audacity. I cause mysite. verizon. net/hal. bower/music. htm), it is rather
it to become unusable on a variety of systems by simply editing a WAV file.
Since I use this feature quite regularly for cleaning up my old vinyl
records (see http://
important to me. This problem exists with the audacity_1.3.4xxx package but
is absent under earlier 1.2.4 and 1.2.6 packages on Hardy (although my crude
efforts to make them work broke the package system), and all efforts to
configure with different options were fruitless.
The symptoms can be seen by the following procedure:
1. Edit a 2:30 to 4:00 minute WAV file
2. Remove (or add) a few tenths of second leadin
3. Go to end of file and cut 0.5 Secs or more from end
4. Try to save the file (Export as WAV). Sometimes it will, others not
At this point, CPU usage (from gkrellm and top from another window) goes to
100% with about 2/3 attributable to X and 1/3 to audacity, yet nothing moves
or seems to refresh in the audacity window. I have left things this way for
20 minutes (with the CPU getting gradually hotter) with no change. The rest
of the system is usable and audacity can be killed from a terminal window.
This had been verified on:
- Biostar Turion 3200 Motherboard with ATI AIW 7500 video, CF 8GB hda
- Biostar Sempron64 3000 Motherboard (as above w/onboard VIA video)
- EeePC 4g (Mobile Celeron 900 MHz, Intel 915 graphics)
- EeeBox (where dual-threading altered CPU loads but similar results)
Intel Atom 1.6 GHz, Intel 945 graphics.
As a result, I still keep a Dapper Drake system in daily use.