This sure sounds like the issues that lead to me creating this thread:
And to the one pointed out by @marc_boule here:
Note, for me, this problem is worse in Rack 2.1.1 than in 2.1.0 , but, since I have been able to totally avoid this crash by not doing any module resets automatically with a small delay after patch load, I have quit worrying about it, even though I know there is still an apparent bug in Rack 2.1.0 and 2.1.1 .
With this bug, it seemed sensitive to connecting cables to modules when editing the patch, but was impossible for me to track down what was happening.
By the way, I did have a crash bug in an early version of Meander for V2 that was related to connecting cables to my module and how I was handling internal detection of those connections. Basically, I was accessing the CableWidget in my ModuleWidget:: step() override. I had to add the isComplete() check on the CableWidget object before doing anything with it.
Don’t know if this is relevant, but I have never discussed this here.
for (CableWidget* cwOut : APP->scene->rack->getCablesOnPort(outPortWidgets[Meander::OUT_CLOCK_BEATX8_OUTPUT]))
{
if (!cwOut->isComplete()) // new for testing, from vcvrack-packone strip.cpp
continue;
if (cwOut->cable->id == cwIn->cable->id)
{
module->theMeanderState.theHarmonyParms.STEP_inport_connected_to_Meander_trigger_port=Meander::OUT_CLOCK_BEATX8_OUTPUT;
}
}