Comment 5 for bug 1817628

Marking X/B as verification done.

The user reports the issue occurs much less often now.
Apparently that environment hits some corner case or this may still be expected sometimes under memory pressure (i.e., one big shrinking operation acquired the lock and must finish).

Nonetheless, the fix reduced the frequency the problem occurs, so it does address most of that and is beneficial on its own.

As discussed with @klebers on IRC, in this scenario we agreed to ship the fix, and address the pending behavior (if an actual issue) with additional fixes later.

cheers,
Mauricio