Tony Thompson wrote:
> I have seen this pop up on occasion with 4.2.15rc0.
> Any idea why?
It is another of those wierd memory boundary issues! A member
variable is manipulated within sync blocks but used outside of
a sync block. On some SMP machines, this means that out-of-order
updates may be seen!
I think this was only exposed by the fix that was done for 15rc0
for a similar problem on the job variable.
I fix is going in now.
Get latest updates about Open Source Projects, Conferences and News.