| |
|
In a message dated 2007-11-17 01:07 Eastern Standard Time,
audacity-users-request@li... writes:
Subject: [Audacity-users] deadlock with bad ownership of temporary
directory (fwd)
To: audacity-users@li...
Message-ID:
<Pine.LNX.4.63.0711162007530.24246@t-...>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
This bugreport was sent to the apparetly broken list audacity-help. I
resend it here.
/Viktor
---------- Forwarded message ----------
Date: Wed, 24 Oct 2007 23:15:33 +0200 (CEST)
From: Viktor Griph <griph@st...>
To: audacity-help@li...
Subject: deadlock with bad ownership of temporary directory
Version: Audacity v1.3.2-beta (Unicode) (on gentoo)
If audacity is started with an already existing /tmp/audacity1.2-$LOGNAME,
with
another owner than the current uid audacity will deadlock upon stopping a
recording.
To reproduce:
1. create the directory /tmp/audacity1.2-$LOGNAME using some diferent user,
och
change ownership of that directory
2. start audacity
3. hit the record button
4. hit stop
At this point audacity will stopp redrawing. Interrupt in the terminal
starting
audacity terminates it.
Secondly if, one during the recording instead of hitting stop starts to
select
portions of the sample, or does other things with the sample autdacity will
start to output loas 2048 samples repetedly, and will eventually crash with
a
segmentaion fault. This is not 100% reproducable.
/Viktor
are you running windows?
if so go to my computer
control panel
internet options
under general
click delete temporary internet files
check include offline content.
dlete them twice.
you don;t need to delete cookies.
also try purging your temp files.
to do so;
click start
run
type (without the quotes) " TEMP% "
right click inside the folder, choose sort by modified.
highlight anything more than a week or two old (keep your cookie and
temporary internet files if your particular build of windows has them there) by left
clicking the 1st file, then while holding shift click the last (oldest )
file, this should highlight all of them
click file, click DELETE.
re-launch audacity.
see if the issue returns.
if so;
are you running freeware VST plugs?
if so, remove them all from the audacity plugins folder, and relaunch
audacity and see if the issue returns.
if not, then re-add vst's one or two at a time untill the problem reoccurs.
if this happens, it's a fouled VST crashing audacity.
next, please understand, if you try to HIGHLIGHT something while it is
atually playing in audacity, you will most definitely crash the GUI of the
program, possibly resulting in damage to audacity itself. you can click anywhere in
the wav display to find a point, but highlighting etc is best done when it's
not running...it takes a lot of resources for some computers to draw this
dynamic visual display, and i'm pretty surethat the lion's share of the used
RAM while the program is running is devoted to the GUI....so if you're trying
to highlight it while running, you may be overloading the capacity of your
machine...
mine will definitely screw up, i'm running a p4 @ 2.7 ghz with a gig of ram
(not crazy fast anymore, but useful for my purposes) and tell ya what, you
can DEFINITELY crash it by overloading the gui, particularly if you have a lot
of tracks running simultaneoulsy...
the computer needs to draw these and re-draw them as fast as the size of the
display is set at...like, if you're looking at the project in total on the
screen, or magnified.
you may wanna reinstall the program for ALL users, as that may aleviate your
problem, as well.
i don;t think it's an audacity bug as much as a windows one.
good luck dude
your mileage may vary.
;)
pinkster
"Our society is run by insane people for insane objectives. I think
we're being run by maniacs for maniacal ends and I think I'm liable to
be put away as insane for expressing that. That's what's insane about
it."
John Lennon (1940 - 1980)
************************************** See what's new at http://www.aol.com
|
|
