rustc consumes > 50GB memory, completes eventually but def. stuck on something

First of all, I am convinced it is more the fault of me doing something wrong. My hope and guess is that this is not a bug in rust, but just me misusing the language. I can however not find why it is happening, but I imagine it is something to do with an accidantal recursive trait bound or other generic related issue...

• Problem is specifically with: https://github.com/plabayo/rama/blob/09c8bc0fea80560763c12149aceae3d9ddae87f5/examples/http_high_level_client.rs
• And it seemed to have been introduced the "problem" in https://github.com/plabayo/rama/pull/297/commits/aa4ea25cd2e4d624e8f82d1c48d375f285e3266b (that's when CI stage timings increased from 12m to 85m...)

Of course it might be that already before aa4ea25cd2e4d624e8f82d1c48d375f285e3266b I was defining trait bounds or using generics in a "wrong" manner.

Logs attached for timings I was able to produce with nightly (in stable it was taking too long for me to be able to wait):

rustc.logs.zip

Start with examples/http_high_level_client.rs at the linked revision and compare it with commit aa4ea25cd2e4d624e8f82d1c48d375f285e3266b. Review rustc.logs.zip and reproduce the compilation timing and memory use with nightly or stable. Done means identifying a minimized compiler issue or confirming the behavior is caused by the example's trait bounds or generics.