[Bug,1.3.9] Crash when using much RAM

[Mampf]

I am using the newest Beta on Windows 7 (32bit!) and am trying to apply a low-pass filter to a quite long (90 minutes) audio file.

I monitor the usage of memory by Audacity, and every time it just disappeared when using about 1900000KB of physical RAM without any hint.
(I have 4 GB of which 3,4 are usable by the OS.)

I wonder if this occurs on 64bit systems as well.

Can the program's behaviour be modified somehow so that it doesn't have to deal with such large chunks of data?

I've tried editing half of the file at a time, but this still was too much.
At least Windows managed to show a dialogue that Audacity isn't responding anymore this time.

Overall memory usage during the appliance of the filter:

[kozikowski]

Audacity is something of a coal mine canary. It fails when your computer is sick.

Since you seem to have a good touchy-feely relationship with your RAM, can I assume you bought and installed it yourself? Did you get a good deal? Can you send it back if you find a dead stick?

http://oca.microsoft.com/en/windiag.asp

Run it all night.

Koz

[Mampf]

I'll try that. If you have faith in your RAM, please try the above-mentioned procedure yourself and see what happens? Only takes three minutes.

I used the equalizer effect instead now and it worked fine in the several runs and I achieved what I intended.


Edit: Since that creates just a bootable image, I'll just run the memtest from my Ubuntu CD instead. Thanks for the suggestion anyway. (:

[kozikowski]

<<<Only takes three minutes.>>>

That's the quick version and that's per pass. You need multiple passes of the long version to turn up ratty hardware. I had one ratty stick, one bad power supply, and a damaged motherboard (on different computers). None of them failed on the first pass.

Pass 15 - Galloping Dog Test - F0F0F0F0 in F0F0E0F0 out - Error on Module.......

This problem will be back. Audacity uses up all the resources available in real time and if they fail, so does Audacity.

Koz

[steve]

Can the program's behaviour be modified somehow so that it doesn't have to deal with such large chunks of data?

This is a known problem with Nyquist effects in Audacity 1.3.9
It has been fixed in Audacity 1.3.10 alpha

If you would like to try the latest alpha version it is available here: http://wiki.audacityteam.org/index.php? ... tly_Builds