<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Issue</th>
<td>
<a href=https://github.com/llvm/llvm-project/issues/106283>106283</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>
[LLDB] lldb-server busyloops on Windows
</td>
</tr>
<tr>
<th>Labels</th>
<td>
new issue
</td>
</tr>
<tr>
<th>Assignees</th>
<td>
DavidSpickett,
ZequanWu
</td>
</tr>
<tr>
<th>Reporter</th>
<td>
mstorsjo
</td>
</tr>
</table>
<pre>
After receiving a connection from a client, lldb-server seems to essentially busyloop.
To reproduce:
In one terminal:
```
> lldb-server.exe g localhost:9090
```
In a second terminal:
```
> lldb.exe
(lldb) process connect --plugin gdb-remote connect://localhost:9090
```
After connecting to the `lldb-server` process, that process starts consuming 100% cpu on one thread. In this case, the `MainLoopWindows::Poll()` method returns immediately each time it is called.
While busylooping, `lldb-server` does seem to work as expected - it just seems to use CPU excessively while doing that.
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJyUU8Fu4zYQ_RrqMrBAU5ZsHXTwxg2wQAos0BYBeqPIicQsRaqckZP8fUHZzmbbvQQQJGgGnPf43htN5IaA2In6i1DqpM_O_jE78x2ZhVJC3Qml_sZ_Fh0el1yoT4VeeIypm4hjoudY9NG-dccnxgQJDbqzCwNoMDEENOxigKcUp1zxDgMLdQfe235DmM6YgBAnAo6ARBjYae_foF_ozcc4l0KehDxe3n9GSDinaBeDojp-bH0NEAMCY5pc0P4_XdHI63P5rX77yKDEV4QBfDTaj5FYVMdWtvLXR29oGghNDPaTkBnrWlGHXBCqhTlFg0Q3xWCzmf0yuACD7TcJp8h462UUdS_U_SfYXqy52RGGrDWPCKKRH1QQjbwRyQ7xqPmdGLFOvPKjZcoTtlIKVYOZF4hX5ceE2pbwNQCPjsBowsucFeh37cJDjPOjCza-UL5GdfwWvRfqIFSbwSfkMVpIyEsKBG6a0DrN6N8AtRmB3YTgGNbh3qP9KRuPo_P4HhsXhgz-_xvaiLQmLovwEtN30AT4OqNhtLDJ858X4h-hXAjh7ttfgK9ZCXfOdF5WLBtXLUfNZWG7yrZVqwvstnu127fb-tAUY4c7LXv11Cu73TfNvjGyt6pRUppqb7TsC9cpqXbyoPZK7hpVl22tq_bQYr_Fun3aKrGTOGnnS-_PUxnTUDiiBbutbNShKrzu0dN1ewO-wNq9Lmrq8qFNvwwkdtI7Yvoxhh37de0fHk5fRH36aSdvOlK29-pZsSTfjcwzvYdwcDwufWnilBPpz7fPZk7xOadV3a98SKj7K-Fzp_4NAAD__zkKaXk">