Affects Version/s: 21.3
Fix Version/s: None
From Alexander Petrovsky email@example.com to Erlang Questions Mailing List:
Dear maintainers, during perf test I stumble upon that application freeze, don't respond to erlang pings, don't accept any new connections and don't write any logs. Seems like one of the Erlang schedulers got stuck in an endless loop.
- top -H
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
15977 hbc 20 0 5103668 1.6g 5764 R 99.9 21.5 10:23.40 4_scheduler
The trace from gdb attached. Is any additional information required?
Additional, steps to reproduce from my colleague:
- cat ./loop-rep.gdb
- gdb --pid 32025 -x ./loop-rep.gdb
where pid 32025 is scheduler thread pid