BUG: Different results with parallel Curve/Curve intersection

I am getting data sorted into the wrong trees when my Curve/Curve intersection component is run in Parallel mode in the Rhino BETA - the results are different from the normal mode. See attached:
parallel_ccx-bug.gh (15.3 KB)

Little late but I can confirm. The branch order is off when encountering Null values.
See attached image.

Using Rhino 6.4

run into this as well running on Win 10, no parallel mode, will there be a fix or how would we go around it for the time being?

Can confirm this as well. I also created my own thread, it seems like DavidRutten will have a look at it.