A hang has been observed in CI which appears to be a lost wake up or concurrency hole pertaining to the dirty list in write cache service.
I am going to file this as "critical" since we need to keep an eye on it while working to clean up CI and prepare the next release.
Likely explanations include:
- resource leakage under CI;
- JVM lost signal (this used to be a problem in some 1.6 releases and who knows what's up with the OSX JVMs. The workaround was to enable the "membar" option to the JVM. This has since been fixed in standard JVM releases
- since 1.6.0_18 if I recall.)
- incorrect propagation of an interrupt, dropped exception, etc.