apache / apache/servicecomb-java-chassis
2.8.4 ZipkinProviderDelegate中的responseWrapper会保存服务端返回的response，且不会被销毁
Open
- Dominant language
- Java
- Stars
- 1.9k
- Forks
- 814
- Avg merge
- 8d 23h
- Merged PRs (30d)
- 1
Description
如果一个请求的响应数据过大，且只被调用一次，则可能会出现其所占用的内存一直不被释放的情况
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating ZipkinProviderDelegate and tracing how responseWrapper stores the server response across a request. Reproduce the issue with an oversized response that is called only once, then inspect the wrapper's cleanup or release lifecycle. Done means the response is no longer retained after the request and a regression test demonstrates that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100