Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 8e39ddd8 authored by Steven Moreland's avatar Steven Moreland
Browse files

Revert "Only spawn one binder thread for cmd." 

This was being used as a work around for a static destructor
issue that has been fixed.

This reverts commit c21bc9af.
Bug: 36066697
Bug: 77934844
Test: cmd still works

Change-Id: Id13589c5c12de0a36b70b8d16216e21345eb986e
parent be3de8b3

cmds/cmd/cmd.cpp

+0 −7
Original line number Diff line number Diff line
@@ -167,13 +167,6 @@ int main(int argc, char* const argv[]) 
{

    signal(SIGPIPE, SIG_IGN);

    sp<ProcessState> proc = ProcessState::self();

    // setThreadPoolMaxThreadCount(0) actually tells the kernel it's

    // not allowed to spawn any additional threads, but we still spawn

    // a binder thread from userspace when we call startThreadPool().

    // This is safe because we only have 2 callbacks, neither of which

    // block.

    // See b/36066697 for rationale

    proc->setThreadPoolMaxThreadCount(0);

    proc->startThreadPool();



#if DEBUG