av_lockmgr_register doesn't destroy the mutex

[John]

Hello,
av_lockmgr_register doesn't invoke callBack function with AV_LOCK_DESTROY after using a mutex;
log:

Create a mutex
Create a mutex
Lock the mutex
Unlock the mutex
Lock the mutex
Unlock the mutex
Lock the mutex
Unlock the mutex
Lock the mutex
Unlock the mutex
Lock the mutex
Unlock the mutex
Lock the mutex
Unlock the mutex
Lock the mutex
Unlock the mutex
Lock the mutex
Unlock the mutex
Lock the mutex
Unlock the mutex
Lock the mutex
Unlock the mutex
Lock the mutex
Unlock the mutex
Lock the mutex
Unlock the mutex

[Hendrik]

At which point would you expect the mutex to be destroyed?
From that log, it seems you only call the register function once, it creates the two mutex objects it uses, and then just locks/unlocks them. It would only destroy them once you call it again.

[John]

I expect that function must itself destroy the mutex after all manipulations, because it creates them

[Hendrik]

And how would it know that you're done using it?
For all it knows, you may continue calling the APIs at any moment.

When your application closes, just call the register function with a NULL argument, and it will destroy the mutex.