compromised lock throws error when release is called

[pimlie]

Is it intended behaviour that calling release for a lock which has been compromised throws an error? It feels counter-intuitive to me. Maybe we could add a strict mode, which is default true but when its false a compromised lock doesnt throw an error?

[satazor]

I agree. Can you change to not throw? This will have to be a major though because it’s a breaking change.

[linonetwo]

It always throws "Lock is already released", and make CPU usage 100%.