Comment 2 for bug 1775497

I think while creating mappings for my self-built controller I may have experienced the same, or at least a related issue/crash.

Mixxx version in use is the latest 2.3 beta
My default routing for each deck is "crossfader bus through effect unit" (so FX L and FX R enabled)

For each deck I created a button-mapping which does the following if pressed (here for Deck1):

engine.setValue("[EffectRack1_EffectUnit1]", "group_[Channel1]_enable", 1);
engine.setValue("[EffectRack1_EffectUnit1]", "group_[BusLeft]_enable", 0);
engine.setValue("[EffectRack1_EffectUnit1_Effect3]", "enabled", 1);

For the sake of completeness - EffectRack1_EffectUnitX_Effect3 is an echo effect with the following same parameters for each deck:

Time: 0.5
Feedback: 0.7
Ping Pong: 0
Feedback: 0.7

On releasing the button all changes are reverted:

engine.setValue("[EffectRack1_EffectUnit1]", "group_[Channel1]_enable", 0);
engine.setValue("[EffectRack1_EffectUnit1]", "group_[BusLeft]_enable", 1);
engine.setValue("[EffectRack1_EffectUnit1_Effect3]", "enabled", 0);

The setup seemed to work fine, but after a while of just playing around (pressing the buttons for each deck randomly) Mixxx crashed due to a "segmentation fault" or "memory access violation" - the original german message is: Speicherzugriffsfehler (Speicherabzug geschrieben).

This issue is reproducible, even without any tracks loaded (with empty decks) - start Mixxx and use the above-mentioned controller mapping. Usually after 10-100 button presses the crash happens.

I was not able to observe a certain behaviour like "crash happens only if you press buttons for each deck simultaneously" or "if you press button long enough, for x seconds" or similar.

Hope this helps to identify the problem!

Happy Easter everyone!