Project

General

Profile

Bug #10168

Updated by François ARMAND about 7 years ago

We observed a case where a generation can't end.  

 It seems to be link to the call of "cachedCompliance.invalidate(updatedNodeIds)", which is synchronized.  
 I'm not sure why it can terminate during a generation - in fact, maybe it is not a dead lock, and invalidate is just very, very long. But there is no reason the whole generation is blocked by that. generation.

Back