RC2, 2012 sp2
Exposed InputChannel gives a weird list…
Does it do it always? I am trying to figure out when it happens. It seems to be some form of memory corruption on the MXS side in the Custom Attribute, possibly due to the array length… I used to see it more often before, now I haven’t seen it in a while, but probably did not expose that input often enough…
I would even consider removing the ability to Expose inputChannel nodes for v1.0 until we find out what is causing this.
Ok, I rewrote the portion that deals with exposing the channels list.
In the original implementation, the channel list array was stored in the node as a custom property and then read from there when a re-exposure was needed.
But there is no need to do this intermediate saving, I just rewrote it to pull the current input channels list and sort it at the time of exposure. The list is then stored in the Custom Attribure as .items array.
So if we assume that the corruption was caused by the storing of the array as a custom property in the Genome inputChannel node, this should now be fixed.
If the corruption is actually caused by the Custom Attribute’s definition itself, then it would continue to happen.
The attached scripts are the latest version for 1.0, please give them a try with build v0.9.2 when you have the time and see if anything changes…
Genome_Scripts_20120411.zip (91.9 KB)
That may have fixed it. At least the case I was seeing is now fixed.