Closed tap closed 4 years ago
Here is another example of the same crash using min.phasor~ with input coming from the scheduler thread. The source of this report is Cycling74/min-devkit#139
{
"boxes" : [ {
"box" : {
"maxclass" : "newobj",
"text" : "mtof",
"id" : "obj-3",
"patching_rect" : [ 193.0, 159.0, 32.0, 22.0 ],
"outlettype" : [ "" ],
"numinlets" : 1,
"numoutlets" : 1
}
}
, {
"box" : {
"maxclass" : "newobj",
"text" : "notein",
"id" : "obj-2",
"patching_rect" : [ 169.0, 66.0, 41.0, 22.0 ],
"outlettype" : [ "int", "int", "int" ],
"numinlets" : 1,
"numoutlets" : 3
}
}
, {
"box" : {
"maxclass" : "newobj",
"text" : "min.phasor~",
"id" : "obj-1",
"patching_rect" : [ 217.0, 228.0, 75.0, 22.0 ],
"outlettype" : [ "signal" ],
"numinlets" : 1,
"numoutlets" : 1
}
}
],
"lines" : [ {
"patchline" : {
"source" : [ "obj-3", 0 ],
"destination" : [ "obj-1", 0 ]
}
}
, {
"patchline" : {
"source" : [ "obj-2", 0 ],
"destination" : [ "obj-3", 0 ]
}
}
],
"appversion" : {
"major" : 8,
"minor" : 1,
"revision" : 1,
"architecture" : "x64",
"modernui" : 1
}
,
"classnamespace" : "box"
}
Report from MR:
I've also personally seen this in the context of the rad.waveslice~ help patcher (a project on a local machine).