Segmentation fault on changing key to a very very low value

Bug #1684845 reported by Wihola IT
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
In Progress
Critical
Unassigned

Bug Description

I have made a midi mapping for an infinite rotary that can change a key. If making it lower and lower, at some point mixxx will crash.

Tags: crash easy key
Revision history for this message
Wihola IT (wihola) wrote :
Revision history for this message
Wihola IT (wihola) wrote :
Revision history for this message
Be (be.ing) wrote :

From the backtrace it looks like you are using SoundTouch. Does this also occur if you use Rubberband? You can switch between them in the Sound Hardware Preferences (that is admittedly a confusing place for that preference option).

Revision history for this message
Wihola IT (wihola) wrote :

Debug [Controller]: "__control: "
Debug [Controller]: "CMD PL-1 MIDI 1: outgoing: status 0xB0 (ch 1, opcode 0xB), ctrl 0x04, val 0x97"
Resampler::process: libsamplerate error: SRC ratio outside [1/256, 256] range.
terminate called after throwing an instance of 'RubberBand::Resampler::Exception'
Aborted

I understand that this is cheating, and I need to make a javascript function works the smart way. But I still can crash mixxx with a dumb way.

Revision history for this message
Wihola IT (wihola) wrote :

The same occurs if I will make the pitch higher and higher in the Rubberband mode.

Revision history for this message
Daniel Schürmann (daschuer) wrote :

I can confirm this, [Channel1],pitch = 30 works and [Channel1],pitch = 40 -> crash (Soundtouch)
Rubberband crashes later, at least at 300.
I think a good band aid is to limit these values to a reasonable number.

Changed in mixxx:
status: New → Confirmed
importance: Undecided → Critical
milestone: none → 2.1.0
Revision history for this message
Daniel Schürmann (daschuer) wrote :

@Wihola IT: do you have fun to adopt this bug?

Revision history for this message
Wihola IT (wihola) wrote :

@daschuer, yes.

Wihola IT (wihola)
Changed in mixxx:
assignee: nobody → Wihola IT (wihola)
Revision history for this message
Be (be.ing) wrote :

Wihola IT, have you made any progress working on this bug or should someone else take it up for 2.1?

Be (be.ing)
Changed in mixxx:
assignee: Wihola IT (wihola) → nobody
Revision history for this message
Wihola IT (wihola) wrote : Re: [Bug 1684845] Re: Segmentation fault on changing key to a very very low value

Hello Be. I am not going to make it.

On 11.11.17 18:13, Be wrote:
> Wihola IT, have you made any progress working on this bug or should
> someone else take it up for 2.1?
>

Revision history for this message
Wihola IT (wihola) wrote :

I am not able to make it.

Revision history for this message
Be (be.ing) wrote :

Considering this only affects an edge case and has only been reported by one user, I am demoting it from Critical to High. If someone wants to step up to take care of this for 2.1, reassign it to that milestone.

Changed in mixxx:
importance: Critical → High
milestone: 2.1.0 → none
RJ Skerry-Ryan (rryan)
Changed in mixxx:
importance: High → Critical
tags: removed: pitch segfault
Revision history for this message
Jan Holthuis (holthuis-jan) wrote :

I can still reproduce this. If I set `[Channel1],pitch` or `[Channel1],pitch_adjust` to 100, it still works. If I set it to 200, mixxx is killed with `SIGKILL` automatically.

Revision history for this message
Jan Holthuis (holthuis-jan) wrote :

This should be rather easy to fix. Just clamp the value to a reasonable range, like -30 or 30, using the `connectValueChangeRequested` mechanism.

tags: added: easy
Revision history for this message
ronso0 (ronso0) wrote (last edit ):
Changed in mixxx:
status: Confirmed → In Progress
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/8847

lock status: Metadata changes locked and limited to project staff
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.