Deadlock with simultaneous generation and new reports
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.
#4 Updated by Vincent MEMBRÉ 9 months ago
- Status changed from Pending release to Released