Heap Corruption using ofSoundStream on Windows

Hello,

I’ve noticed that setting the ofSoundStream bufferSize above 128 causes a heap corruption on some Windows systems, while it works fine on other Windows systems. All other platforms work fine.

I did not find any similarities on the system where the heap corruption occurs.

Sample code to reproduce:

#include "ofApp.h"

ofSoundStream soundStream;
//--------------------------------------------------------------
void ofApp::setup(){
    // crashes on some systems if > 128)
    int bufferSize = 129;

    soundStream.setup(this, 2, 0, 44100, bufferSize, 4);
}


//--------------------------------------------------------------
void ofApp::update(){

}

//--------------------------------------------------------------
void ofApp::draw(){
    static int i = 0;
    // wait a little bit, dont stop instantly after setup
    if (i == 200) {
        soundStream.stop(); //heap corruption!
    }
    i++;
}


//--------------------------------------------------------------
void ofApp::keyPressed  (int key){

}

//--------------------------------------------------------------
void ofApp::keyReleased  (int key){

}

//--------------------------------------------------------------
void ofApp::mouseMoved(int x, int y ){

}

//--------------------------------------------------------------
void ofApp::mouseDragged(int x, int y, int button){

}

//--------------------------------------------------------------
void ofApp::mousePressed(int x, int y, int button){

}


//--------------------------------------------------------------
void ofApp::mouseReleased(int x, int y, int button){

}

//--------------------------------------------------------------
void ofApp::mouseEntered(int x, int y){

}

//--------------------------------------------------------------
void ofApp::mouseExited(int x, int y){

}

//--------------------------------------------------------------
void ofApp::windowResized(int w, int h){

}

//--------------------------------------------------------------
void ofApp::gotMessage(ofMessage msg){

}

//--------------------------------------------------------------
void ofApp::dragEvent(ofDragInfo dragInfo){ 

}

Is this an openFrameworks bug?

Use the provided C++ sample as the reproduction entry point: call ofSoundStream::setup with bufferSize 129 on affected Windows systems, wait, then call stop(). Trace the Windows audio-stream setup and shutdown path; done means reproducing and preventing heap corruption for buffer sizes above 128 without breaking other platforms.