Bug 528248 - idle audacity causes CPU to go to 85 degrees C.
Summary: idle audacity causes CPU to go to 85 degrees C.
Keywords:
Status: CLOSED DUPLICATE of bug 494425
Alias: None
Product: Fedora
Classification: Fedora
Component: audacity
Version: 10
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gérard Milmeister
QA Contact: Fedora Extras Quality Assurance
URL: http://sourceforge.net/mailarchive/me...
Whiteboard:
Depends On: 494425
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-10-10 01:12 UTC by Dave Allan
Modified: 2016-04-26 16:01 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2009-10-12 15:56:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dave Allan 2009-10-10 01:12:19 UTC
Description of problem:
I left audacity running but idle with an audio file (wav) loaded, and noticed several hours later that my laptop's fan was running constantly and heat was pouring out of the heatsink, which turned out to be because the processors had gotten up to 85C.  I'm afraid I didn't do much but check to see what process was working the processors, which turned out to be audacity, and quit it, after which the laptop returned to normal, so I have no further information to report, but I think it's worth seeing if this behavior reproduces on rawhide since it's kind of nasty.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. load up a wav in audacity (mine is a fairly large one, 53MB)
2. go away for a few hours

Comment 1 Michael Schwendt 2009-10-10 08:34:18 UTC
Doesn't need to be Rawhide. For Fedora 11 there is a test-update for Audacity 1.3.9-beta. Are you limited to Fedora 10?

Comment 2 Michael Schwendt 2009-10-10 08:59:35 UTC
Very likely the same than bug 494425, albeit with older Audacity but also wxGTK 2.8.10.

Comment 3 Michael Schwendt 2009-10-12 15:56:30 UTC

*** This bug has been marked as a duplicate of bug 494425 ***

Comment 4 Dave Allan 2009-10-23 17:33:48 UTC
Upgrading to wxGTK-2.8.10-3.fc10.i386 fixed it.


Note You need to log in before you can comment on or make changes to this bug.