Stress-test to detect any memory leaks etc.

[edsko]

The main test suite is concerned with behaviour, not resource usage. We need to have a serious stress test, making thousands and thousands of connections, and thousands and thousands of calls on each connection, and verify that no resources get leaked. Might perhaps be useful to limit the heap and the stack size when we run these tests.

May require some changes to http2; see discussion in kazu-yamamoto/http2#78 .

[FinleyMcIlwaine]

Implemented part of this at #134, still need to implement the many-messages stress test. We also should stress test a situation where many reconnections happen.

[edsko]

We also need to add a test to reproduce #169 here (i.e., many concurrent calls).

[edsko]

When we close this issue, there are a few references to this ticket in the codebase that we should check and, if indeed handled, delete.