maxbear1988

Results 8 comments of maxbear1988

memory leak when processing h2 protocol requests

this bytes bug will cause oom.https://github.com/tokio-rs/bytes/issues/559 @seanmonstar

memory leak when processing h2 protocol requests

@seanmonstar i keep sending request in h2 with 6k body with the same client. Memory keep growing.i use jemalloc to dump jeprof file,and find most memories are alloc by slab....

HTTP/2 should send a reset of NO_ERROR instead of CANCEL if already sent response headers

@seanmonstar thank you. i don't think it is related to SSL. It it performance well in http1.1；if i read the request body，it performance well in http2.0,too. Does hyper send a...

HTTP/2 should send a reset of NO_ERROR instead of CANCEL if already sent response headers

@seanmonstar chrome report ERR_HTTP2_PROTOCOL_ERROR ，not ERR_SSL_PROTOCOL_ERROR ，i wrote error last time

HTTP/2 should send a reset of NO_ERROR instead of CANCEL if already sent response headers

@seanmonstar yes，i try chrome，firefox，Microsoft Edge，all report ERR_HTTP2_PROTOCOL_ERROR

HTTP/2 should send a reset of NO_ERROR instead of CANCEL if already sent response headers

@seanmonstar if i read all request body, then response status code 413, it is ok. if i response status code 413 without reading request body, it is not ok.I think...

HTTP/2 should send a reset of NO_ERROR instead of CANCEL if already sent response headers

@seanmonstar i open hyper trace log，hyper send reset frame with error_code CANCEL. FramedWrite::buffer{frame=Reset { stream_id: StreamId(647), error_code: CANCEL

HTTP/2 should send a reset of NO_ERROR instead of CANCEL if already sent response headers

@seanmonstar do you have a plan to fix this issue?