Comment 4 for bug 430637

The initial description related to a test which was run with max_connections=120, set as a command-line parameter on server startup.
The same problem happens if a test is run with default max_connections value 151 (pbxt_max_threads=158).
In both cases neither max_connections nor pbxt_max_threads are changed during the test.
.
The attached archive contains a test which might help to reproduce the problem. It executes exactly the same flow as the test provided for bug#430641, but it also turns on event scheduler and sets up several events (with very short time intervals to get processes pile up faster).

The usage is exactly the same as for the test in bug#430641.