Add support for Location (RTC_FROM_HERE) to ProcessThread::RegisterModule.
This makes a few things a lot clearer when looking at perf trace data: * What module instances (where they were created) are called * On what thread * How frequently * For how long ProcessThread will be replaced by TaskQueue moving forward and this is a step towards understanding the behavior of the affected code. BUG=webrtc:7219 Review-Url: https://codereview.webrtc.org/2729053002 Cr-Commit-Position: refs/heads/master@{#16998}
This commit is contained in:
@ -13,8 +13,8 @@
|
||||
|
||||
#include <memory>
|
||||
|
||||
#include "webrtc/base/location.h"
|
||||
#include "webrtc/modules/utility/include/process_thread.h"
|
||||
|
||||
#include "webrtc/test/gmock.h"
|
||||
|
||||
namespace webrtc {
|
||||
@ -29,7 +29,7 @@ class MockProcessThread : public ProcessThread {
|
||||
MOCK_METHOD0(Stop, void());
|
||||
MOCK_METHOD1(WakeUp, void(Module* module));
|
||||
MOCK_METHOD1(PostTask, void(rtc::QueuedTask* task));
|
||||
MOCK_METHOD1(RegisterModule, void(Module* module));
|
||||
MOCK_METHOD2(RegisterModule, void(Module* module, const rtc::Location&));
|
||||
MOCK_METHOD1(DeRegisterModule, void(Module* module));
|
||||
|
||||
// MOCK_METHOD1 gets confused with mocking this method, so we work around it
|
||||
|
||||
Reference in New Issue
Block a user