Audacity runs fairly good, work environment acts up

[Dr. Killjoy]

Interesting. I've been looking at the system monitor, and as I can see, it only uses around 665 MB of random access memory, not swap memory. Which is explained by the 1 mb blocks Audacity project are built from.

Could it have been the graphics card driver, perhaps? I don't see why this would affect only Audacity, but I've changed it several times, now using a third-party closed driver for ATI Radeon, but I can now type this message and run Audacity at the same time. To me, it's not an explanation, but perhaps to someone else?

I'm using fglrx-updates in stead of fglrx (2.9.010) or xserver-xorg-video-ati. Both of which I used beforehand (after re-installing).

[steve]

Could it have been the graphics card driver, perhaps?

It's possible.
When possible, Audacity use a cache for the waveform display, but often the waveform needs to be updated, Updating the waveform is pretty heavy duty stuff - sometimes taking longer to calculate than the actual audio processing. I've not much experience with video driver issues on Linux as I've had few problems in that area (I've mostly used Intel or NVidea graphics on Linux).

[Gale Andrews]

I've noticed (while "extreme testing") that Audacity has a serious problem with Swap.

Would it be useful to post something in the Bug Triage board about that?

Is it a crash or just unreasonably slow?


Gale

[steve]

I've noticed (while "extreme testing") that Audacity has a serious problem with Swap.

Would it be useful to post something in the Bug Triage board about that?

Is it a crash or just unreasonably slow?

The only way that I can reproduce the issue is with Nyquist - normally Audacity uses very little RAM on my machine. With reference to Nyquist I think it is already on bugzilla, though I suspect that the problem goes beyond Nyquist (suggested by the problems that occurred when we had the option to use RAM as the temporary data location).

[Gale Andrews]

I've noticed (while "extreme testing") that Audacity has a serious problem with Swap.

Would it be useful to post something in the Bug Triage board about that?

Is it a crash or just unreasonably slow?

The only way that I can reproduce the issue is with Nyquist - normally Audacity uses very little RAM on my machine. With reference to Nyquist I think it is already on bugzilla, though I suspect that the problem goes beyond Nyquist (suggested by the problems that occurred when we had the option to use RAM as the temporary data location).

Perhaps, but that Audio Cache feature could certainly crash without Audacity using the swap file at all.


Gale