-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIGSEGV in SoundTouch 1.9.2 #8534
Comments
Commented by: ywwg in the past we've had crashes when either soundtouch or rubberband were fed "crazy" rates, like 0 or 10000000000. So this might be a case where we aren't successfully detecting an invalid rate. |
Commented by: uklotzde Before the crash it played for 2 hours without any issues so I don't think this is caused by some weird parameter. Looks more like a memory corruption issue. |
Commented by: rryan Uwe -- I could never reproduce the segfault so I'm not sure if I fixed it. But maybe we can declare it fixed and reopen if someone sees it again. I also enabled asan in our Travis builds so we should notice memory safety bugs like this in the future at PR-time. |
Commented by: rryan (assuming the tests exercise the code path :X) |
Commented by: rryan The overflow was only at bootup though -- but maybe it trashed some internal soundtouch or engine state that caused your segfault. |
Commented by: wrobertson1981 Thread 11 "mixxx" received signal SIGSEGV, Segmentation fault. Crash while using the library-redesign branch, 1 1/2 hours into a set. Possible regression. How do I trigger this problem, reliably? |
Commented by: daschuer Could you remember what your rate slider and keylock state was just before the crash? |
Commented by: daschuer A similar bug is fixed here: |
Commented by: wrobertson1981 uhh... 1.9.2.2-2, the latest is 1.9.2-3... there is no soundtouch 2 released for ubuntu as far as i know? |
Commented by: wrobertson1981 Switching to Rubberband to play it safe. |
Commented by: daschuer So we need to provide Soundtouch ourselves for Ubuntu as well. |
Commented by: daschuer The upstream bug is tracked here: |
Commented by: janitor Status changed to 'Confirmed' because the bug affects multiple users. |
Commented by: Be-ing
IMO that should only be done in extreme circumstances. It would be better to work with Ubuntu to update their Soundtouch package. Fedora 28 is shipping Soundtouch 2.0. Arch is as well. |
Commented by: daschuer I have already assigned this bug to them. What else can we do? |
Commented by: Be-ing
|
Commented by: uklotzde Why not simply increasing the minimum required version from 1.8.0 to 2.0.0? |
Commented by: wrobertson1981 Huh? and break the easy installation of Mixxx until Debian/ubuntu update the package? |
Commented by: daschuer
Yes, that is the way to go here. Trusty for example has Soundtouch 1.7 so we build it with our own static library anyway. If Ubuntu has 2.0.0 one day, it will uses the system provided version again. |
Commented by: s-ramacher 2.0.0 is now available in Ubuntu. FWIW, the Debian Multimedia Team does not receive notifications from Launchpad. So if you require actions from us, please file bugs in the Debian bug tracker or contact the mailing list. |
Commented by: daschuer We now use our own sounddouch 2.0 if the distro provided version is lower. |
Issue closed with status Fix Released. |
Reported by: uklotzde
Date: 2016-04-30T19:21:40Z
Status: Fix Released
Importance: Critical
Launchpad Issue: lp1577042
OS: Fedora 23 x86_64
Lib: soundtouch-1.9.2-3.fc23.x86_64
Branch: master (2.1.0-alpha-pre x64)
Key Lock enabled
Pitch at 0.00
- not moved during the whole session (AutoDJ background music @home)
File plays fine after restart
- same results
- waveform generation is skipped now
The text was updated successfully, but these errors were encountered: