|
|
|
Stevethefiddle
|
Ubuntu 9.04, Audacity 1.3.9 / 1.3.10
To reproduce: 1) Generate a track 2) Play 3) Adjust the "Transcription Toolbar" slider to a slower speed while track is playing. Audacity stops and locks up. This is a nasty crash as the entire Desktop stops responding, requiring "F2 > killall audacity > Enter" (can't even click on "OK"). Increasing the playback speed will trigger the crash most of the time. Reducing the playback speed triggers the crash 10 times out of 10. Does not seem to be a problem on Win XP. Steve D ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
| From Steve <[hidden email]> | Fri, 23 Oct 2009 09:19:28 +0100 | Subject: [Audacity-devel] Linux crash when adjusting playback speed while playing > Ubuntu 9.04, Audacity 1.3.9 / 1.3.10 > > To reproduce: > 1) Generate a track > 2) Play > 3) Adjust the "Transcription Toolbar" slider to a slower speed while > track is playing. > > Audacity stops and locks up. > > This is a nasty crash as the entire Desktop stops responding, requiring > "F2 > killall audacity > Enter" (can't even click on "OK"). > > Increasing the playback speed will trigger the crash most of the time. > Reducing the playback speed triggers the crash 10 times out of 10. > > Does not seem to be a problem on Win XP. I can't actually reproduce that on Ubuntu 9.04 in CVS HEAD Unicode Release from a couple of days ago. I tried both starting playback with the normal Play button and with Transcription Toolbar's own button, and playing a region and playing from the cursor. Are there any other factors such as length of track or region, playback device (ALSA default here) or the value on the toolbar slider before you change it? Gale ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Stevethefiddle
|
Gale Andrews wrote:
> | From Steve <[hidden email]> > | Fri, 23 Oct 2009 09:19:28 +0100 > | Subject: [Audacity-devel] Linux crash when adjusting playback speed while playing > >> Ubuntu 9.04, Audacity 1.3.9 / 1.3.10 >> >> To reproduce: >> 1) Generate a track >> 2) Play >> 3) Adjust the "Transcription Toolbar" slider to a slower speed while >> track is playing. >> >> Audacity stops and locks up. >> >> This is a nasty crash as the entire Desktop stops responding, requiring >> "F2 > killall audacity > Enter" (can't even click on "OK"). >> >> Increasing the playback speed will trigger the crash most of the time. >> Reducing the playback speed triggers the crash 10 times out of 10. >> >> Does not seem to be a problem on Win XP. >> > > I can't actually reproduce that on Ubuntu 9.04 in CVS HEAD Unicode > Release from a couple of days ago. I tried both starting playback with > the normal Play button and with Transcription Toolbar's own button, > and playing a region and playing from the cursor. > > Are there any other factors such as length of track or region, playback > device (ALSA default here) or the value on the toolbar slider before you > change it? > > > > > Gale Host (ALSA) and "default" settings for devices. Also tried other settings, but still get this issue. There do not appear to be any special cases, it always crashes when moving the transcription speed slider slower. I've just tested with Audacity 1.3.7 and that's fine. Also tested with Audacity 1.3.9 on Windows XP running in Virtual Box (on the same computer) and that's fine also. Steve D ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Stevethefiddle
|
In reply to this post
by Gale (Audacity Team)
Gale Andrews wrote:
> | From Steve <[hidden email]> > | Fri, 23 Oct 2009 09:19:28 +0100 > | Subject: [Audacity-devel] Linux crash when adjusting playback speed while playing > >> Ubuntu 9.04, Audacity 1.3.9 / 1.3.10 >> >> To reproduce: >> 1) Generate a track >> 2) Play >> 3) Adjust the "Transcription Toolbar" slider to a slower speed while >> track is playing. >> >> Audacity stops and locks up. >> >> This is a nasty crash as the entire Desktop stops responding, requiring >> "F2 > killall audacity > Enter" (can't even click on "OK"). >> >> Increasing the playback speed will trigger the crash most of the time. >> Reducing the playback speed triggers the crash 10 times out of 10. >> >> Does not seem to be a problem on Win XP. >> > > I can't actually reproduce that on Ubuntu 9.04 in CVS HEAD Unicode > Release from a couple of days ago. I tried both starting playback with > the normal Play button and with Transcription Toolbar's own button, > and playing a region and playing from the cursor. > > Are there any other factors such as length of track or region, playback > device (ALSA default here) or the value on the toolbar slider before you > change it? > > > > > Gale > same - still crashes. Steve ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
| From Steve D <[hidden email]> | Sat, 24 Oct 2009 23:07:36 +0100 | Subject: [Audacity-devel] Linux crash when adjusting playback speed while playing > Gale Andrews wrote: > > | From Steve <[hidden email]> > > | Fri, 23 Oct 2009 09:19:28 +0100 > > | Subject: [Audacity-devel] Linux crash when adjusting playback speed while playing > > > >> Ubuntu 9.04, Audacity 1.3.9 / 1.3.10 > >> > >> To reproduce: > >> 1) Generate a track > >> 2) Play > >> 3) Adjust the "Transcription Toolbar" slider to a slower speed while > >> track is playing. > >> > >> Audacity stops and locks up. > >> > >> This is a nasty crash as the entire Desktop stops responding, requiring > >> "F2 > killall audacity > Enter" (can't even click on "OK"). > >> > >> Increasing the playback speed will trigger the crash most of the time. > >> Reducing the playback speed triggers the crash 10 times out of 10. > >> > >> Does not seem to be a problem on Win XP. > >> > > > > I can't actually reproduce that on Ubuntu 9.04 in CVS HEAD Unicode > > Release from a couple of days ago. I tried both starting playback with > > the normal Play button and with Transcription Toolbar's own button, > > and playing a region and playing from the cursor. > > > > Are there any other factors such as length of track or region, playback > > device (ALSA default here) or the value on the toolbar slider before you > > change it? > > > > > > > > > > Gale > > > Just made a fresh install from cvs with all default settings - just the > same - still crashes. OK, go to the Keyboard tab of Preferences, choose the "Command" category and add shortcuts for the last four items (Play at Speed and *playback speed). Does it still crash if you use the shortcuts, not the slider? Otherwise, compile with --enable-debug and run Audacity under gdb? gdb -ex run ./audacity If there's a crash, gdb will give you a prompt that allows further investigation. For example, the "bt" command prints a backtrace. See: http://www.gnu.org/software/gdb/documentation/ Note, I've never done this, I'm just suggesting this may be the next step. Gale ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Stevethefiddle
|
Gale Andrews wrote:
> | From Steve D <[hidden email]> > | Sat, 24 Oct 2009 23:07:36 +0100 > | Subject: [Audacity-devel] Linux crash when adjusting playback speed while playing > >> Gale Andrews wrote: >> >>> | From Steve <[hidden email]> >>> | Fri, 23 Oct 2009 09:19:28 +0100 >>> | Subject: [Audacity-devel] Linux crash when adjusting playback speed while playing >>> >>> >>>> Ubuntu 9.04, Audacity 1.3.9 / 1.3.10 >>>> >>>> To reproduce: >>>> 1) Generate a track >>>> 2) Play >>>> 3) Adjust the "Transcription Toolbar" slider to a slower speed while >>>> track is playing. >>>> >>>> Audacity stops and locks up. >>>> >>>> This is a nasty crash as the entire Desktop stops responding, requiring >>>> "F2 > killall audacity > Enter" (can't even click on "OK"). >>>> >>>> Increasing the playback speed will trigger the crash most of the time. >>>> Reducing the playback speed triggers the crash 10 times out of 10. >>>> >>>> Does not seem to be a problem on Win XP. >>>> >>>> >>> I can't actually reproduce that on Ubuntu 9.04 in CVS HEAD Unicode >>> Release from a couple of days ago. I tried both starting playback with >>> the normal Play button and with Transcription Toolbar's own button, >>> and playing a region and playing from the cursor. >>> >>> Are there any other factors such as length of track or region, playback >>> device (ALSA default here) or the value on the toolbar slider before you >>> change it? >>> >>> >>> >>> >>> Gale >>> >>> >> Just made a fresh install from cvs with all default settings - just the >> same - still crashes. >> > > OK, go to the Keyboard tab of Preferences, choose the "Command" > category and add shortcuts for the last four items (Play at Speed and > *playback speed). Does it still crash if you use the shortcuts, not the > slider? > This gives a marked improvement, though I can still get it to lock up if I go mad with it. I've looked more closely at what I am doing to create the issue and it is when I DRAG the slider that the problem occurs. If I just CLICK on the transcription slider scale, then the track playback restarts from the original cursor position at the new speed (which I presume is the correct behaviour). It looks like a rapid sequence of "change playback speed" commands creates some kind of overflow that locks up Audacity. I've just checked again in Audacity 1.3.7 and I can drag the slider without any problem. > Otherwise, compile with --enable-debug and run Audacity under gdb? > > gdb -ex run ./audacity > > If there's a crash, gdb will give you a prompt that allows further > investigation. For example, the "bt" command prints a backtrace. > > See: > http://www.gnu.org/software/gdb/documentation/ > > Note, I've never done this, I'm just suggesting this may be the next > step. > > > > > > Gale > when I get back. Steve D ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Al Dimond
|
On Sunday 25 October 2009 04:55:36 Steve D wrote:
> Gale Andrews wrote: > > | From Steve D <[hidden email]> > > | Sat, 24 Oct 2009 23:07:36 +0100 > > | Subject: [Audacity-devel] Linux crash when adjusting playback > > | speed while playing > >> > >> Gale Andrews wrote: > >>> | From Steve <[hidden email]> > >>> | Fri, 23 Oct 2009 09:19:28 +0100 > >>> | Subject: [Audacity-devel] Linux crash when adjusting playback > >>> | speed while playing > >>>> > >>>> Ubuntu 9.04, Audacity 1.3.9 / 1.3.10 > >>>> > >>>> To reproduce: > >>>> 1) Generate a track > >>>> 2) Play > >>>> 3) Adjust the "Transcription Toolbar" slider to a slower speed > >>>> while track is playing. > >>>> > >>>> Audacity stops and locks up. > >>>> > >>>> This is a nasty crash as the entire Desktop stops responding, > >>>> requiring "F2 > killall audacity > Enter" (can't even click on > >>>> "OK"). > >>>> > >>>> Increasing the playback speed will trigger the crash most of > >>>> the time. Reducing the playback speed triggers the crash 10 > >>>> times out of 10. > >>>> > >>>> Does not seem to be a problem on Win XP. > >>> > >>> I can't actually reproduce that on Ubuntu 9.04 in CVS HEAD > >>> Unicode Release from a couple of days ago. I tried both > >>> starting playback with the normal Play button and with > >>> Transcription Toolbar's own button, and playing a region and > >>> playing from the cursor. > >>> > >>> Are there any other factors such as length of track or region, > >>> playback device (ALSA default here) or the value on the toolbar > >>> slider before you change it? > >>> > >>> > >>> > >>> > >>> Gale > >> > >> Just made a fresh install from cvs with all default settings - > >> just the same - still crashes. > > > > OK, go to the Keyboard tab of Preferences, choose the "Command" > > category and add shortcuts for the last four items (Play at Speed > > and *playback speed). Does it still crash if you use the > > shortcuts, not the slider? > > This gives a marked improvement, though I can still get it to lock > up if I go mad with it. > > I've looked more closely at what I am doing to create the issue and > it is when I DRAG the slider that the problem occurs. If I just > CLICK on the transcription slider scale, then the track playback > restarts from the original cursor position at the new speed (which > I presume is the correct behaviour). > > It looks like a rapid sequence of "change playback speed" commands > creates some kind of overflow that locks up Audacity. > I've just checked again in Audacity 1.3.7 and I can drag the slider > without any problem. > I can reproduce this easily. As far as I can tell, there's no actual crash, just a hang. I'm working on figuring out exactly what's going on. > > Otherwise, compile with --enable-debug and run Audacity under > > gdb? > > > > gdb -ex run ./audacity > > > > If there's a crash, gdb will give you a prompt that allows > > further investigation. For example, the "bt" command prints a > > backtrace. > > > > See: > > http://www.gnu.org/software/gdb/documentation/ > > > > Note, I've never done this, I'm just suggesting this may be the > > next step. > > > > > > > > > > > > Gale > > Thanks, I'm packing to go away for a few days so I'll look into > that when I get back. > Running Audacity (and other X11 apps) in GDB is perilous because of keyboard and mouse grabs. I added a section to the wiki about this: http://wiki.audacityteam.org/index.php?title=Developing_On_Linux#Problems_with_GDB_and_keyboard.2Fmouse_grabs Actually, the reason all your mouse clicks are getting swallowed until you kill audacity is that while you're dragging the slider Audacity grabs the mouse, not allowing other programs to get clicks. Because Audacity hangs, it never releases the mouse, so you're stuck until you kill Audacity. On the Wiki I suggest using a nested X server for running Audacity in GDB, and that might also make your life easier while testing this bug, since the mouse grab would only affect the inner server. > Steve D > > ------------------------------------------------------------------- > ----------- Come build with us! The BlackBerry(R) Developer > Conference in SF, CA is the only developer event you need to > attend this year. Jumpstart your developing skills, take > BlackBerry mobile applications to market and stay ahead of the > curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > audacity-devel mailing list > [hidden email] > https://lists.sourceforge.net/lists/listinfo/audacity-devel > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
| From Al Dimond <[hidden email]> | Sun, 25 Oct 2009 17:32:15 -0600 | Subject: [Audacity-devel] Linux crash when adjusting playback speed while playing > On Sunday 25 October 2009 04:55:36 Steve D wrote: > > Gale Andrews wrote: > > > | From Steve D <[hidden email]> > > > | Sat, 24 Oct 2009 23:07:36 +0100 > > > | Subject: [Audacity-devel] Linux crash when adjusting playback > > > | speed while playing > > >> > > >> Gale Andrews wrote: > > >>> | From Steve <[hidden email]> > > >>> | Fri, 23 Oct 2009 09:19:28 +0100 > > >>> | Subject: [Audacity-devel] Linux crash when adjusting playback > > >>> | speed while playing > > >>>> > > >>>> Ubuntu 9.04, Audacity 1.3.9 / 1.3.10 > > >>>> > > >>>> To reproduce: > > >>>> 1) Generate a track > > >>>> 2) Play > > >>>> 3) Adjust the "Transcription Toolbar" slider to a slower speed > > >>>> while track is playing. > > >>>> > > >>>> Audacity stops and locks up. > > >>>> > > >>>> This is a nasty crash as the entire Desktop stops responding, > > >>>> requiring "F2 > killall audacity > Enter" (can't even click on > > >>>> "OK"). > > >>>> > > >>>> Increasing the playback speed will trigger the crash most of > > >>>> the time. Reducing the playback speed triggers the crash 10 > > >>>> times out of 10. > > >>>> > > >>>> Does not seem to be a problem on Win XP. > > >>> > > >>> I can't actually reproduce that on Ubuntu 9.04 in CVS HEAD > > >>> Unicode Release from a couple of days ago. I tried both > > >>> starting playback with the normal Play button and with > > >>> Transcription Toolbar's own button, and playing a region and > > >>> playing from the cursor. > > >>> > > >>> Are there any other factors such as length of track or region, > > >>> playback device (ALSA default here) or the value on the toolbar > > >>> slider before you change it? > > >>> Gale > > >> > > >> Just made a fresh install from cvs with all default settings - > > >> just the same - still crashes. > > > > > > OK, go to the Keyboard tab of Preferences, choose the "Command" > > > category and add shortcuts for the last four items (Play at Speed > > > and *playback speed). Does it still crash if you use the > > > shortcuts, not the slider? > > > > This gives a marked improvement, though I can still get it to lock > > up if I go mad with it. > > > > I've looked more closely at what I am doing to create the issue and > > it is when I DRAG the slider that the problem occurs. If I just > > CLICK on the transcription slider scale, then the track playback > > restarts from the original cursor position at the new speed (which > > I presume is the correct behaviour). > > > > It looks like a rapid sequence of "change playback speed" commands > > creates some kind of overflow that locks up Audacity. > > I've just checked again in Audacity 1.3.7 and I can drag the slider > > without any problem. > > > > I can reproduce this easily. As far as I can tell, there's no actual > crash, just a hang. I'm working on figuring out exactly what's going > on. Try as I might, unreproducible for me (GNOME, if that makes any difference). >From what I recall, having the playback cursor go back to time zero when dragging the play-at-speed slider was the best we could do at the time that did not create other problems. > > > Otherwise, compile with --enable-debug and run Audacity under > > > gdb? > > > > > > gdb -ex run ./audacity > > > > > > If there's a crash, gdb will give you a prompt that allows > > > further investigation. For example, the "bt" command prints a > > > backtrace. > > > > > > See: > > > http://www.gnu.org/software/gdb/documentation/ > > > > > > Note, I've never done this, I'm just suggesting this may be the > > > next step. > > > Gale > > > > Thanks, I'm packing to go away for a few days so I'll look into > > that when I get back. > > > > Running Audacity (and other X11 apps) in GDB is perilous because of > keyboard and mouse grabs. I added a section to the wiki about this: > > http://wiki.audacityteam.org/index.php?title=Developing_On_Linux#Problems_with_GDB_and_keyboard.2Fmouse_grabs Thanks for that, Al. Gale > Actually, the reason all your mouse clicks are getting swallowed until > you kill audacity is that while you're dragging the slider Audacity > grabs the mouse, not allowing other programs to get clicks. Because > Audacity hangs, it never releases the mouse, so you're stuck until you > kill Audacity. On the Wiki I suggest using a nested X server for > running Audacity in GDB, and that might also make your life easier > while testing this bug, since the mouse grab would only affect the > inner server. > > > Steve D ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Stevethefiddle
|
In reply to this post
by Al Dimond
Al Dimond wrote:
> On Sunday 25 October 2009 04:55:36 Steve D wrote: > >> Gale Andrews wrote: >> >>> | From Steve D <[hidden email]> >>> | Sat, 24 Oct 2009 23:07:36 +0100 >>> | Subject: [Audacity-devel] Linux crash when adjusting playback >>> | speed while playing >>> >>>> Gale Andrews wrote: >>>> >>>>> | From Steve <[hidden email]> >>>>> | Fri, 23 Oct 2009 09:19:28 +0100 >>>>> | Subject: [Audacity-devel] Linux crash when adjusting playback >>>>> | speed while playing >>>>> >>>>>> Ubuntu 9.04, Audacity 1.3.9 / 1.3.10 >>>>>> >>>>>> To reproduce: >>>>>> 1) Generate a track >>>>>> 2) Play >>>>>> 3) Adjust the "Transcription Toolbar" slider to a slower speed >>>>>> while track is playing. >>>>>> >>>>>> Audacity stops and locks up. >>>>>> >>>>>> This is a nasty crash as the entire Desktop stops responding, >>>>>> requiring "F2 > killall audacity > Enter" (can't even click on >>>>>> "OK"). >>>>>> >>>>>> Increasing the playback speed will trigger the crash most of >>>>>> the time. Reducing the playback speed triggers the crash 10 >>>>>> times out of 10. >>>>>> >>>>>> Does not seem to be a problem on Win XP. >>>>>> >>>>> I can't actually reproduce that on Ubuntu 9.04 in CVS HEAD >>>>> Unicode Release from a couple of days ago. I tried both >>>>> starting playback with the normal Play button and with >>>>> Transcription Toolbar's own button, and playing a region and >>>>> playing from the cursor. >>>>> >>>>> Are there any other factors such as length of track or region, >>>>> playback device (ALSA default here) or the value on the toolbar >>>>> slider before you change it? >>>>> >>>>> >>>>> >>>>> >>>>> Gale >>>>> >>>> Just made a fresh install from cvs with all default settings - >>>> just the same - still crashes. >>>> >>> OK, go to the Keyboard tab of Preferences, choose the "Command" >>> category and add shortcuts for the last four items (Play at Speed >>> and *playback speed). Does it still crash if you use the >>> shortcuts, not the slider? >>> >> This gives a marked improvement, though I can still get it to lock >> up if I go mad with it. >> >> I've looked more closely at what I am doing to create the issue and >> it is when I DRAG the slider that the problem occurs. If I just >> CLICK on the transcription slider scale, then the track playback >> restarts from the original cursor position at the new speed (which >> I presume is the correct behaviour). >> >> It looks like a rapid sequence of "change playback speed" commands >> creates some kind of overflow that locks up Audacity. >> I've just checked again in Audacity 1.3.7 and I can drag the slider >> without any problem. >> >> > > I can reproduce this easily. As far as I can tell, there's no actual > crash, just a hang. I'm working on figuring out exactly what's going > on. > > >>> Otherwise, compile with --enable-debug and run Audacity under >>> gdb? >>> >>> gdb -ex run ./audacity >>> >>> If there's a crash, gdb will give you a prompt that allows >>> further investigation. For example, the "bt" command prints a >>> backtrace. >>> >>> See: >>> http://www.gnu.org/software/gdb/documentation/ >>> >>> Note, I've never done this, I'm just suggesting this may be the >>> next step. >>> >>> >>> >>> >>> >>> Gale >>> >> Thanks, I'm packing to go away for a few days so I'll look into >> that when I get back. >> >> > > Running Audacity (and other X11 apps) in GDB is perilous because of > keyboard and mouse grabs. I added a section to the wiki about this: > > http://wiki.audacityteam.org/index.php?title=Developing_On_Linux#Problems_with_GDB_and_keyboard.2Fmouse_grabs > > Actually, the reason all your mouse clicks are getting swallowed until > you kill audacity is that while you're dragging the slider Audacity > grabs the mouse, not allowing other programs to get clicks. Because > Audacity hangs, it never releases the mouse, so you're stuck until you > kill Audacity. On the Wiki I suggest using a nested X server for > running Audacity in GDB, and that might also make your life easier > while testing this bug, since the mouse grab would only affect the > inner server. > > I've got Xephyr up and running with wm2. gdb is installed and appears to be OK, but can't build Audacity with --enable-debug option. Have updated the Audacity source from cvs, but still getting lots (hundreds) of errors when running "make" and can not get it to complete. I'm using wxWidgets 2.8.10.1-1 with the dbg package. Is this version too new/old? Am I missing an important configuration step? If I run "make" without the debug option there appears to be no problem. There are no obvious errors when running ./configure --enable-debug Steve D ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Al Dimond
|
On Thursday 29 October 2009 10:23:41 Steve D wrote:
> Getting there, but getting stuck. > > I've got Xephyr up and running with wm2. > gdb is installed and appears to be OK, > but can't build Audacity with --enable-debug option. > > Have updated the Audacity source from cvs, but still getting lots > (hundreds) of errors when running "make" and can not get it to > complete. > > I'm using wxWidgets 2.8.10.1-1 with the dbg package. > Is this version too new/old? Am I missing an important > configuration step? > I used to have problems with this, then I installed a lot more -dbg and -dev packages and it worked. Perhaps there should be some documentation of what packages you need to build with --enable-debug. > If I run "make" without the debug option there appears to be no > problem. There are no obvious errors when running ./configure > --enable-debug > What are the first few error lines? Typically when there are lots of errors the first few point to the problem and the rest are the result of the first error. GCC spew can be really hard to read, but if you redirect it to files like so: make > outfile 2> errfile you can search through the resulting files for the first line containing "error". > Steve D > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Al Dimond
|
In reply to this post
by Stevethefiddle
On Sunday 25 October 2009 04:55:36 Steve D wrote:
> > OK, go to the Keyboard tab of Preferences, choose the "Command" > > category and add shortcuts for the last four items (Play at Speed > > and *playback speed). Does it still crash if you use the > > shortcuts, not the slider? > > This gives a marked improvement, though I can still get it to lock > up if I go mad with it. > > I've looked more closely at what I am doing to create the issue and > it is when I DRAG the slider that the problem occurs. If I just > CLICK on the transcription slider scale, then the track playback > restarts from the original cursor position at the new speed (which > I presume is the correct behaviour). > > It looks like a rapid sequence of "change playback speed" commands > creates some kind of overflow that locks up Audacity. > I've just checked again in Audacity 1.3.7 and I can drag the slider > without any problem. > I see this same behavior. When I break in after the lock-up, whether through clicking like crazy or dragging, I always see something almost exactly like this: (gdb) info threads 798 Thread 0x7fffdd5b0910 (LWP 9154) pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261 797 Thread 0x7fffe1db2910 (LWP 9153) __pthread_mutex_lock_full (mutex=0x2603c30) at pthread_mutex_lock.c:303 6 Thread 0x7fffe25b3910 (LWP 8356) 0x00007ffff3ac48f1 in nanosleep () from /lib/libpthread.so.0 * 1 Thread 0x7ffff7fb47f0 (LWP 8349) 0x00007ffff3abdcfd in pthread_join (threadid=140736907118864, thread_return=0x7fffffffd138) at pthread_join.c:89 I don't know a lot about pthreads, but it looks like Thread 1 is waiting on thread 798: (gdb) bt #0 0x00007ffff3abdcfd in pthread_join (threadid=140736907118864, thread_return=0x7fffffffd138) at pthread_join.c:89 ... (gdb) printf "%llx\n", threadid 7fffdd5b0910 Thread 1 traces back to AudioIO::StopStream(), on a call to Pa_AbortStream(). Thread 798's backtrace looks like: (gdb) bt #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261 #1 0x00007fffe6e4442b in pa_threaded_mainloop_wait () from /usr/lib/libpulse.so.0 #2 0x00007fffe65b92aa in pulse_wait_operation () from /usr/lib/alsa- lib/libasound_module_pcm_pulse.so #3 0x00007fffe65b8774 in ?? () from /usr/lib/alsa- lib/libasound_module_pcm_pulse.so #4 0x00007ffff3f69867 in ?? () from /usr/lib/libasound.so.2 #5 0x0000000000955c09 in AlsaStop (stream=0x25d1270, abort=128) at src/hostapi/alsa/pa_linux_alsa.c:2196 #6 0x0000000000956bea in OnExit (data=0x25d1270) at src/hostapi/alsa/pa_linux_alsa.c:2513 #7 0x000000000095b598 in CallbackThreadFunc (userData=<value optimized out>) at src/hostapi/alsa/pa_linux_alsa.c:3251 #8 0x00007ffff3abca04 in start_thread (arg=<value optimized out>) at pthread_create.c:300 #9 0x00007ffff307b7bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #10 0x0000000000000000 in ?? () What this thread is waiting on is less clear (to me, at least). Seeing pulseaudio stuff on the stack, I went to Preferences and chose my ALSA 0:0 device instead of the pulse device. And the problem went away. As this problem seems to only occur with Pulse, it might also depend on the version of Pulse. I have 0.9.19-0ubuntu4, on Kubuntu 9.10. - Al ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
| From Al Dimond <[hidden email]> | Sat, 31 Oct 2009 20:45:46 -0600 | Subject: [Audacity-devel] Linux crash when adjusting playback speed while playing > On Sunday 25 October 2009 04:55:36 Steve D wrote: > > > OK, go to the Keyboard tab of Preferences, choose the "Command" > > > category and add shortcuts for the last four items (Play at Speed > > > and *playback speed). Does it still crash if you use the > > > shortcuts, not the slider? > > > > This gives a marked improvement, though I can still get it to lock > > up if I go mad with it. > > > > I've looked more closely at what I am doing to create the issue and > > it is when I DRAG the slider that the problem occurs. If I just > > CLICK on the transcription slider scale, then the track playback > > restarts from the original cursor position at the new speed (which > > I presume is the correct behaviour). > > > > It looks like a rapid sequence of "change playback speed" commands > > creates some kind of overflow that locks up Audacity. > > I've just checked again in Audacity 1.3.7 and I can drag the slider > > without any problem. > > I see this same behavior... Seeing pulseaudio stuff on the stack, I went > to Preferences and chose my ALSA 0:0 device instead of the pulse device. > And the problem went away. > > As this problem seems to only occur with Pulse, it might also depend > on the version of Pulse. I have 0.9.19-0ubuntu4, on Kubuntu 9.10. I wasn't using the Pulse device on Ubuntu 9.04, but switched to it and still can't reproduce a lockup (Pulse is "latest available" called "1:0.9.14-0ubuntu20.2"). The only thing I can replicate here (either using Pulse or ALSA 0:0) is that if I go mad and drag the slider back and forth for several seconds then release it, playback will start visually with the cursor moving across the screen at what looks like the requested speed, but there is no sound and no output in the VU playback meter. Sound and metering resumes if I just hit Space twice, but there is no further sound or metering using the Play button on Transcription Toolbar until I restart Audacity. Gale ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Al Dimond
|
On Sunday 01 November 2009 13:49:40 Gale Andrews wrote:
> | From Al Dimond <[hidden email]> > | Sat, 31 Oct 2009 20:45:46 -0600 > | Subject: [Audacity-devel] Linux crash when adjusting playback > | speed while playing > | > > On Sunday 25 October 2009 04:55:36 Steve D wrote: > > > > OK, go to the Keyboard tab of Preferences, choose the > > > > "Command" category and add shortcuts for the last four items > > > > (Play at Speed and *playback speed). Does it still crash if > > > > you use the shortcuts, not the slider? > > > > > > This gives a marked improvement, though I can still get it to > > > lock up if I go mad with it. > > > > > > I've looked more closely at what I am doing to create the issue > > > and it is when I DRAG the slider that the problem occurs. If I > > > just CLICK on the transcription slider scale, then the track > > > playback restarts from the original cursor position at the new > > > speed (which I presume is the correct behaviour). > > > > > > It looks like a rapid sequence of "change playback speed" > > > commands creates some kind of overflow that locks up Audacity. > > > I've just checked again in Audacity 1.3.7 and I can drag the > > > slider without any problem. > > > > I see this same behavior... Seeing pulseaudio stuff on the > > stack, I went to Preferences and chose my ALSA 0:0 device instead > > of the pulse device. And the problem went away. > > > > As this problem seems to only occur with Pulse, it might also > > depend on the version of Pulse. I have 0.9.19-0ubuntu4, on > > Kubuntu 9.10. > > I wasn't using the Pulse device on Ubuntu 9.04, but switched to it > and still can't reproduce a lockup (Pulse is "latest available" > called "1:0.9.14-0ubuntu20.2"). > OK; we do have different Pulse versions, which could have something to do with it. My best guess is that this is a bug in the PulseAudio client libraries, or whatever is connecting PortAudio's ALSA output up to Pulse (the Pulse server continues to work perfectly). I'm going to try to contact Pulse people about this, if nothing else, to find out more about debugging this sort of thing. Here is additional information I've found (using GDB and the Pulse sources): - Using a normal ALSA output device there appears to be just one audio playback thread that starts when you play and stop when you stop. With Pulse there's a second thread that starts and stops several times at the start/end of playback. Audacity only knows about the first one. - During the hang Audacity's main thread has called pthread_cancel() on the first audio thread, and is waiting for it to finish in a pthread_join(). The first audio thread is waiting in a pthread_cond_wait(), presumably to be signaled by the second audio thread. The second thread is stuck on a pthread_mutex_lock(). The mutex released by the first thread's pthread_cond_wait() is the same as the one the second thread is stuck on. I don't know where the mutex is being held -- I don't know what other thread could be holding it... it could be that the second audio thread already held it, causing a deadlock. > The only thing I can replicate here (either using Pulse or ALSA > 0:0) is that if I go mad and drag the slider back and forth for > several seconds then release it, playback will start visually with > the cursor moving across the screen at what looks like the > requested speed, but there is no sound and no output in the VU > playback meter. Sound and metering resumes if I just hit Space > twice, but there is no further sound or metering using the Play > button on Transcription Toolbar until I restart Audacity. > > > > Gale > > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Richard Ash (audacity-help)
|
On Sun, 2009-11-01 at 22:08 -0600, Al Dimond wrote:
> Here is additional > information I've found (using GDB and the Pulse sources): > > - Using a normal ALSA output device there appears to be just one > audio playback thread that starts when you play and stop when you > stop. With Pulse there's a second thread that starts and stops > several times at the start/end of playback. Audacity only knows about > the first one. This is basically the core of the difference between ALSA and PulseAudio architecturally. ALSA doesn't run threads or a worker daemon, anything that has to be done in userspace to support playback is done in the alsa-lib package which applications are linked to. As a result, such processing ends up in the application's audio I/O thread, which might have performance implications, but eliminates locking and mutextes, so it offers very low latency if required. PulseAudio is a sound server, so has it's own (evidently multi-threaded) daemon running all the time which clients have to connect to. This connection inevitably involves synchronisation via locking/mutexes, which raises the latency. It does make some clever tricks possible that you can't do in ALSA (like network audio output), but not as many as people think, compared to a working ALSA set-up from a recent kernel / userspace. Audacity has a single Audio I/O thread which does the work of pushing audio into the sound device, (plus a disk I/O thread for reads, which is different) which is the one it knows about. Any others have been created by PulseAudio, and are it's problem. In this case I am very much inclined to agree that the problem is an interaction between portaudio and the different versions of PulseAudio. It would be nice to think they have managed to fix something for once, rather than trying to get applications to write yet another audio I/O back-end to connect to PulseAudio. Richard ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Al Dimond
|
In reply to this post
by Gale (Audacity Team)
On Sunday 01 November 2009 13:49:40 Gale Andrews wrote:
> I wasn't using the Pulse device on Ubuntu 9.04, but switched to it > and still can't reproduce a lockup (Pulse is "latest available" > called "1:0.9.14-0ubuntu20.2"). > I opened a PulseAudio ticket for this; they think it might be related to either the alsa-lib or alsa-plugins package. On Ubuntu those are called libasound2 and libasound2-plugins. What version do you have of those? I'm going to run through different versions of alsa-lib/alsa-plugins and libpulse and, if it's a regression somewhere, try to pinpoint it. Thanks - Al ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Gale (Audacity Team)
|
| From Al Dimond <[hidden email]> | Tue, 3 Nov 2009 17:04:52 -0700 | Subject: [Audacity-devel] Linux crash when adjusting playback speed while playing > On Sunday 01 November 2009 13:49:40 Gale Andrews wrote: > > I wasn't using the Pulse device on Ubuntu 9.04, but switched to it > > and still can't reproduce a lockup (Pulse is "latest available" > > called "1:0.9.14-0ubuntu20.2"). > > > > I opened a PulseAudio ticket for this; they think it might be related > to either the alsa-lib or alsa-plugins package. On Ubuntu those are > called libasound2 "1.0.18-1ubuntu9" > and libasound2-plugins. "1.0.18-1ubuntu4" Both of those are the "latest version" for 9.04 (I'm upgrading to 9.10 now). Thanks, Gale > I'm going to run through different versions of alsa-lib/alsa-plugins > and libpulse and, if it's a regression somewhere, try to pinpoint it. > > > Thanks > > - Al ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Arturo 'Buanzo' Busleiman
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512 Gale Andrews wrote: > Both of those are the "latest version" for 9.04 (I'm upgrading to 9.10 > now). You're NOT gonna like that upgrade. - -- Arturo "Buanzo" Busleiman / Arturo Busleiman @ 4:900/107 Independent Linux and Security Consultant - SANS - OISSG - OWASP http://www.buanzo.com.ar/pro/eng.html Mailing List Archives at http://archiver.mailfighter.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREKAAYFAkrw6NAACgkQAlpOsGhXcE1CeACfXJ3HTcZ97hf/Y1OhDqCJTYb1 3QYAn0GML5EL2bEtXMuRrXZsUBEKZgsz =EiTu -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
|
Al Dimond
|
In reply to this post
by Al Dimond
On Tuesday 03 November 2009 17:04:52 Al Dimond wrote:
> > I'm going to run through different versions of > alsa-lib/alsa-plugins and libpulse and, if it's a regression > somewhere, try to pinpoint it. > This doesn't appear to be a regression; all versions of libpulse and alsa-lib/alsa-plugins I've tried exhibit the bug. Furthermore, I haven't been able to isolate the problem in libpulse; I wrote a test program to try to replicate the unusual way we end up using the Pulse API and I haven't seen it yet. Tomorrow I'm going to try caching sampling rates in the AudioIO object because we query PortAudio for them on each playback, which when Pulse is being used means we connect to and disconnect from the server about 15 times in rapid succession. If that doesn't work there are a couple UI workarounds I'm considering, and I'd like to know if anyone has a strong preference between the two, or other ideas. 1. The play-at-speed slider is from our custom ASlider class. I could give the class an optional mode to send slider-changed events when the thumb is released, rather than when it's moved, and then use this mode for the speed slider. 2. I could disable the behavior where playback is restarted when the slider is dragged; the user would be required to click the "play at speed" button to restart the stream at the selected speed. If the current behavior was to continue play from the current playback position I'd consider this a major loss, but since it starts back at the beginning of playback I don't think it matters very much. With the first workaround, and perhaps with the second, it would still be possible to get the hang, but difficult; a user would probably have to be trying to do it. The second method would provide somewhat more protection, at the cost of a larger change in behavior. The other question is, if a change in behavior is made, whether it should apply to all platforms or be isolated to Linux (or all Unix- likes? Pulse could be running anywhere, but I'm not sure all the frontends jerk it around as much as the ALSA plugin). I don't know of a reasonable way to test whether a running audio stream is PulseAudio, or the change could be limited to those. My gut feeling is that we don't want - Al ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ audacity-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/audacity-devel |
||||||||||||||||
| Free Embeddable Forum Powered by Nabble | Help |