高并发下内存泄露和微服务队列拥塞问题

从1.3.0 到现在 2.5.0 版本 ,业务服务原本内存是初始化是1G,MAX 4G,在高tps的冲击下,内存会逐渐增高,直到接近4g,但是如果此时中断业务,内存并不会释放。这会不会框架底层存在内存泄露的情况？

还有一个问题,版本是2.5.0,在接口响应相当慢的时候,频繁冲击业务服务,随后停止业务冲击,发现仍然业务请求打印,持续时间过长,重启服务后恢复.这是否是因为微服务内部队列存在拥塞,即使请求方终止,部分请求会遗留在服务队列中,直至运行完？

@liubao68

No files, tests, or entry points are named. Start by reproducing both reported scenarios across versions 1.3.0 through 2.5.0: monitor memory after high-TPS traffic is stopped and observe whether requests continue after slow-service load ends. Done means identifying a reproducible cause and documenting evidence for memory retention or queue backlog.

Written by the indexing model from the issue text.