MacOS FutureTask.get race (sort of)

[Michael Hall]

On Nov 1, 2011, at 1:19 PM, Jason Schroeder wrote:

> The problem here is that the contract of FutureTask.get is breaking and most likely something is not right at runtime with AbstractQueuedSynchronizer or FutureTask.Sync.
> 
> So far, I have only triggered this problem on MacOS, so I have thought the port team might like to know.

Not familiar with the API yet myself. Odd if incorrect only on OS X. They are sort of independent builds. 
For yours it might make sense to bug report. Since they are independent it would need to be separate bug reports I think.
Not sure you'll see a fix with the Apple since it isn't expected to continue beyond 10.7 as far as I know.
For mine not even reproducible I think I'll just try to figure out where I need the invokeLater.