quininer
@cmazakas I'm sure you realize that's rude. You can make sales pitches any way you like, but please don't comment under other repos all time. It's a spam for the...
We already have `RecvMulti`, it's nice to have `RecvMsgMulti`.
I suspect that using `SeqCst` is not the most reasonable solution, but I'm willing to follow liburing
@FrankReh of course.
I believe we have recently fixed part of this issue (https://github.com/web-infra-dev/rspack/commit/6362a790f5487466eccf723c1dec9fc5a81d629c and https://github.com/web-infra-dev/rspack/commit/d71a6ab6c23f7bab2712fa0d191094c8d2fd26bd), and I will continue to investigate the remaining memory growth causes.
> the memory usage of rsbuild should increase and then decrease later I think this is because of the behavior of mimalloc , which doesn't return memory immediately. and some...
I counted the resident memory between each rebuild. I think that after previous fix, there is no strict leak in rspack rust code in this case. but we still have...
@T9-Forever Did you reproduce it on 1.5.6 using the repro above?
> poll_write calls the underlying poll_write every time. I don't think this is correct, it only calls `poll_write` when it satisfies `wants_write`.
You seem to be right. given that rustls has [a flush method](https://github.com/rustls/rustls/blob/main/rustls/src/conn.rs#L311), this seems to be a reserved behavior for rustls. There are two buffer in write direction, one is...