Message lost of `locks_running` -- may cause deadlock

[xinhaoyuan]

locks_watcher is notified by

locks/src/locks_server.erl

Line 64 in 8e9b2e3

catch locks_watcher ! locks_running,

However, the message could be lost if a locks_server is started after

locks/src/locks_watcher.erl

Line 23 in 8e9b2e3

case whereis(locks_server) of

but the message is sent before the name locks_watcher is registered.

locks/src/locks_watcher.erl

Line 26 in 8e9b2e3

try register(locks_watcher, self()),

[uwiger]

@xinhaoyuan sorry for the long delay, but would you like to inspect the proposed fix?

[xinhaoyuan]

Hi @uwiger, thanks for asking. The fix looks good and should fix the bug reported.

This bug was found using Morpheus, a concurrency testing tool for Erlang. I am no longer working on the project, but I will try to run the tool on the fixed version and let you know if there are any issues.