Noise Removal > Get Noise Profile > Crash

[TheAngryPenguin]

This has been bugging me and is definitely reproducible, albeit only on the Windows platform. Steps to reproduce:

• 1) Open an audio file in Audacity
  2) Select some "noise"
  3) Effect > Noise Removal
  4) Click "Get Noise Profile"

Expected result: Noise Profile is copied to memory
Actual result: Audacity crashes

Code: Select all

Faulting application audacity.exe, version 1.3.3.0, faulting module audacity.exe, version 1.3.3.0, fault address 0x000e1b64.

Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 61 75 64   ure  aud
0018: 61 63 69 74 79 2e 65 78   acity.ex
0020: 65 20 31 2e 33 2e 33 2e   e 1.3.3.
0028: 30 20 69 6e 20 61 75 64   0 in aud
0030: 61 63 69 74 79 2e 65 78   acity.ex
0038: 65 20 31 2e 33 2e 33 2e   e 1.3.3.
0040: 30 20 61 74 20 6f 66 66   0 at off
0048: 73 65 74 20 30 30 30 65   set 000e
0050: 31 62 36 34 0d 0a         1b64..  

This occurs with both the installer and the zip releases, and it occurs whether or not %appdata%Audacity exists. Additionally, it occurs on numerous Windows XP machines (I've tried at least 4 different PCs). FWIW, this does not occur with the OS X build.

[alatham]

Doesn't happen to me at work.

platform:
Windows XP PRO 2002 - w/SP2
Pentium D 3GHz
2G RAM
Dell Optiplex GX620
Soundmax digital audio

I tried it with Wav files, and an MP3. Both 1.2.6 and 1.3.3.

Noise Removal works perfectly for me. I was selecting about .5 seconds of noise.

I wonder if the size of the noise selection has anything to do with it. Perhaps you're selecting too much or too little?

[TheAngryPenguin]

I have tried selecting anywhere from .25 to 1.0 seconds.

[alatham]

I've just tried this on my machine at home. It crashes here.

Gateway 552GE
Pentium 4 - 3.2GHz
1 GB RAM
M-Audio Delta 1010LT
Windows XP Home 2002 w/ SP2

Here's the Error Signature that Windows Reports, the Fault Address is the same as AngryPenguin reported:

Code: Select all

AppName: audacity.exe	 AppVer: 1.3.3.0	 ModName: audacity.exe
ModVer: 1.3.3.0	 Offset: 000e1b64

I didn't think it would help, but I tried disabling all the other added plugins (by changing the name of the plug-ins folder). It didn't do anything useful.

[theeshaneomac]

Yea, it does the same thing to me.

[TheAngryPenguin]

It's good to know that I am not alone. Let me know if there's anything I can do to help resolve this issue.

[alatham]

Well, we need to find the common link that's causing some computers to crash the program and others to survive just fine.

I guess you guys should start by listing the info about your computers that I listed in my other two posts. It's also up to the developers to figure out what that offset value is useful for.

Also, in Audacity's Help -> About box, if you scroll down a little bit there is a section labeled Information: This info might help the developers too. We should also provide this.

Here's the info from my computer at work (the one that does not crash):

Information:

Libmad: Enabled
Ogg Vorbis: Enabled
LibID3Tag: Enabled
FLAC: Enabled
LADSPA: Enabled
Libresample: Enabled
PortAudio v19
wxWidgets 2.6.3
Program build date: May 18 2007
Settings folder: C:Documents and SettingsAndyLApplication DataAudacity

Here's the computer info again:
Dell Optiplex GX620
Windows XP PRO 2002 - w/SP2
Pentium D 3GHz
2G RAM
Soundmax digital audio (on motherboard)

[TheAngryPenguin]

Libmad: Enabled
Ogg Vorbis: Enabled
LibID3Tag: Enabled
FLAC: Enabled
LADSPA: Enabled
Libresample: Enabled
PortAudio v19
wxWidgets 2.6.3
Program build date: May 18 2007
Settings folder: C:Documents and SettingsTheAngryPenguinApplication DataAudacity

System 1
Windows XP Professional w/SP2 running in VMware Fusion on a 1st generation BlackBook
2 GHz Intel Core Duo
2 GB 667 MHz DDR2 SDRAM
Creative AudioPCI (ES1371, ES1373) (WDM)

System 2
Dell PowerEdge 400SC
Windows XP Professional w/SP2
3 GHz Intel Pentium 4
1 GB SDRAM
SoundMAX Integrated Digital Audio

System 3
HP PZ578UA#ABA
Windows XP Professional w/SP2
3 GHz Intel Pentium 4
1 GB SDRAM
SoundMAX Integrated Digital Audio

[Jewelly]

same problem here. I'm off to try a another computer.

[richardash1981]

There is a genuine bug in 1.3.3 causing this. It should be fixed in the 1.3.4 release candidate:
http://audacityteam.org/files/audacity- ... 4rc0.4.exe
http://audacityteam.org/files/audacity- ... 4rc0.4.exe