fatal error: unlock of unlocked mutex

[stefan-shredder]

In what area(s)?

/area runtime

What version of Dapr?

1.13.4

Expected Behavior

When Dapr recovers from an unhealthy state, it shouldn't run into a fatal error while trying to unlock an unlocked mutex.

Actual Behavior

We have different services that run into that behaviour from time to time. The dapr container enters an unhealthy state (for unknown reason) and after it enters the healthy state again, it runs into an fatal error: sync: unlock of unlocked mutex. I have attached the log.

slotbooking-service-868d448f46-6kj59.log

The good part is, that the container successfully recovers from it.

Steps to Reproduce the Problem

Release Note

[yaron2]

Triaged to 1.14

[yaron2]

Can you please ping me on Discord so we can chat ad-hoc about this? My handle is yaron2

[yaron2]

@stefan-shredder can you confirm if this has been fixed in Dapr 1.14.x?

[stefan-schroeder-myleo]

We are on 1.14.4 for about 4 weeks and so far that issue was not raised again.

[yaron2]

Thanks, closing for now