You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "Guillaume Blanc (Jira)" <ji...@apache.org> on 2019/09/20 15:32:00 UTC

[jira] [Created] (THRIFT-4962) Deadlock in TimerManager::stop

Guillaume Blanc created THRIFT-4962:
---------------------------------------

             Summary: Deadlock in TimerManager::stop
                 Key: THRIFT-4962
                 URL: https://issues.apache.org/jira/browse/THRIFT-4962
             Project: Thrift
          Issue Type: Bug
          Components: C++ - Library
    Affects Versions: 0.12.0
            Reporter: Guillaume Blanc
         Attachments: test.cpp

If multiple threads call TimerManager::stop, they will all be waiting on monitor for state to go to STOPPED.
As Dispatcher use monitor_.notify, only one of the thread will be awakened, other will stay waiting forever.

See attached test code to reproduce the issue (timing dependent).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)