Skip to content

Sample-based oscillators could hard crash if a x87 stack overflow happened when calculating the current position in the sample #149

@LeStahL

Description

@LeStahL

This problem is weird - the musician experienced weird native tracker and plugin hard crashes when editing stacks. I boiled the instrument down to this minimal example:

name: rp-Berlin
numvoices: 7
units:
    - type: oscillator
      id: 2
      parameters: {attack: 64, color: 42, decay: 64, detune: 74, gain: 128, looplength: 563, loopstart: 5448, phase: 0, release: 64, samplestart: 143113, shape: 82, stereo: 1, sustain: 64, transpose: 69, type: 4, unison: 1}
    - type: out
      id: 11
      parameters: {auxgain: 64, color: 64, damp: 0, detune: 64, dry: 128, feedback: 96, gain: 64, notetracking: 2, outgain: 64, phase: 0, pregain: 40, shape: 64, stereo: 1, transpose: 64, type: 0}

When disabling or deleting either of the units, the native tracker (and plugin) hard-crash. I collected debug output as well:
sointu_crashlog2.log

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions