Threading bug in referenceCountedArray


#1

I think there’s a bug in ReferenceCountedArray, line 74, the copy constructor.

It copies the size (numUsed) of the array being copied as a constructor initializer (what are those called?) as in : numUsed (other.numUsed), then it locks the other array. I think sometimes an array change is sneaking in between the two.

Bruce


#2

Hmm… sounds like you could be right about that - thanks, I’ll take a look…