When trying to play a file with 0,01x speed, audacity crashes or hangs

Bug #465899 reported by abePdIta
78
This bug affects 1 person
Affects Status Importance Assigned to Milestone
audacity (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: audacity

Moving playback speed slide down to 0.01 causes a crash.

ProblemType: Crash
Architecture: i386
Date: Sat Oct 31 02:09:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/audacity
NonfreeKernelModules: wl
Package: audacity 1.3.9-6
ProcCmdline: audacity
ProcEnviron:
 LANGUAGE=it_IT.UTF-8
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x64f8a83 <memmove+35>: rep movsl %ds:(%esi),%es:(%edi)
 PC (0x064f8a83) ok
 source "%ds:(%esi)" (0x2bbe7577) not located in a known VMA region (needed readable region)!
 destination "%es:(%edi)" (0x0b51424b) ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: audacity
StacktraceTop:
 memmove () from /lib/tls/i686/cmov/libc.so.6
 Mixer::MixVariableRates(int*, WaveTrack*, long long*, float*, int*, int*, Resample*) ()
 Mixer::Process(long long) ()
 AudioIO::FillBuffers() ()
 AudioThread::Entry() ()
Title: audacity crashed with SIGSEGV in memmove()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Revision history for this message
abePdIta (abepdita) wrote :
visibility: private → public
Revision history for this message
David Henningsson (diwic) wrote :

abePdlta, you are recommended to keep your bug private as CoreDump.gz usually contains private data. Instead we wait for the apport retracer to perform a stack trace.

visibility: public → private
Revision history for this message
Benjamin Drung (bdrung) wrote :

The apport data already contains debug information. Therefore a retrace is not required. In this case simply remove the CoreDump.gz and make the bug report public.

visibility: private → public
Revision history for this message
David Henningsson (diwic) wrote :

@Benjamin: I don't think you're correct here. The stack trace that apport makes, is based on the core dump, combined with its internal debug symbols for a lot of packages. Therefore Apport's stack trace will be better than the one provided in the initial bug report.

Revision history for this message
Benjamin Drung (bdrung) wrote :

What is missing in provided stack trace?

Revision history for this message
Frank Cheung (fcuk112) wrote :

abePdIta, can you please let me know 1) if you are able to reproduce this bug. 2) how to reproduce it?

thanks.

Changed in audacity (Ubuntu):
status: New → Incomplete
Revision history for this message
David Henningsson (diwic) wrote :

@Frank: Did you try to reproduce it yourself? When I try here (to playback a file with 0,01 speed), I get the error message "Libsamplerate only supports resampling factors between 1/12 and 12", and then Audacity hangs. So it seems something is wrong here.

@Benjamin: I was hoping for some more variable symbols instead of just "No symbol table info available.".
I'm not an apport retracer expert though, so I'm not 100% sure if I actually would have got some.

Revision history for this message
Frank Cheung (fcuk112) wrote :

David, sorry I wasn't sure how to reproduce the bug but I have just now. Set it back to NEW.

Changed in audacity (Ubuntu):
status: Incomplete → New
Revision history for this message
abePdIta (abepdita) wrote :

Here I am!
I reproduced this bug at least two times consecutively:
- run audacity
- open a file (16 bit, 44100 Hz)
- slide down the playback speed to 0,01 and play at target speed

At this point, in my case, audacity hangs (or close instantly) and then apport shows up.

tags: removed: need-i386-retrace
summary: - audacity crashed with SIGSEGV in memmove()
+ When trying to play a file with 0,01x speed, audacity crashes or hangs
Changed in audacity (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in audacity (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.