Somehow, "Mutex double-freed" has occurred ~200 times in production over the last 30 days.
So far the only possibility I see is maybe there is a way that PromisifiedFS can _deactivate twice, since _deactivationTimeout is written to in two places.
That said, _deactivate itself is written to handle concurrency: you could call it 100 times concurrently, and it should only ever call this._mutex.release() once. So I don't see how this can fix anything.
Somehow, "Mutex double-freed" has occurred ~200 times in production over the last 30 days.
So far the only possibility I see is maybe there is a way that PromisifiedFS can
_deactivate
twice, since_deactivationTimeout
is written to in two places.That said,
_deactivate
itself is written to handle concurrency: you could call it 100 times concurrently, and it should only ever callthis._mutex.release()
once. So I don't see how this can fix anything.