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 c21bc9afe403f52c189d2d6b79dedaf9dce6217b.
Bug: 36066697
Bug: 77934844
Test: cmd still works
Change-Id: Id13589c5c12de0a36b70b8d16216e21345eb986e
diff --git a/cmds/cmd/cmd.cpp b/cmds/cmd/cmd.cpp
index 48d5d4a..4238531 100644
--- a/cmds/cmd/cmd.cpp
+++ b/cmds/cmd/cmd.cpp
@@ -167,13 +167,6 @@
{
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