You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@dubbo.apache.org by GitBox <gi...@apache.org> on 2022/04/18 11:04:30 UTC

[GitHub] [dubbo] hongyu-zxj opened a new issue, #9935: 2.7.10 大response >maxPayload 的异常情况下,出现内存泄露

hongyu-zxj opened a new issue, #9935:
URL: https://github.com/apache/dubbo/issues/9935

   <!-- If you need to report a security issue please visit https://github.com/apache/dubbo/security/policy -->
   
   - [ ] I have searched the [issues](https://github.com/apache/dubbo/issues) of this repository and believe that this is not a duplicate.
   
   ### Environment
   
   * Dubbo version: 2.7.10
   * Operating System version: xxx
   * Java version: 1.8
   
   ### Steps to reproduce this issue
   
   1. 生产者处理大的response
   2. 大于maxPayload ,抛出异常
   3. 内存飙高好几倍,jmap后,内存等不到回收,一直持续,只能重启
   
   Pls. provide [GitHub address] to reproduce this issue.
   
   ### Expected Behavior
   
   <!-- What do you expect from the above steps?-->
   
   ### Actual Behavior
   
   <!-- What actually happens? -->
   
   If there is an exception, please attach the exception trace:
   
   ```
   Just put your stack trace here!
   ```
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org


[GitHub] [dubbo] hongyu-zxj commented on issue #9935: 2.7.10 大response >maxPayload 的异常情况下,出现内存泄露

Posted by GitBox <gi...@apache.org>.
hongyu-zxj commented on issue #9935:
URL: https://github.com/apache/dubbo/issues/9935#issuecomment-1120168883

   可以复现一下,复现方法准备:本地通过visualvm 工具来监听 内存情况,先准备两个dubbo接口,一个是正常调用,一个是response大于maxPayload (建议大于100M左右,太小的我也没有复现)的异常接口;复现步骤:1、调用正常的dubbo接口,查看visualvm 的 byte[]内存情况和MySQLValueObject对象内存占比情况,接口正常返回后再点击visualvm的 perForm GC 触发full GC,再查看 byte[]内存情况和MySQLValueObject对象内存情况;会看到byte[]的内存占比基本恢复到调用前端的情况,MySQLValueObject 对象也消失回收了;2、调用准备好的异常接口,查看visualvm 的 byte[]内存情况和MySQLValueObject对象内存占比情况,可以看到这两项的内存都升高了,而且等接口正常返回了后,这两项的内存占比没有降下去,点击visualvm的 perForm GC 触发full GC后,这两项的内存占比依旧在,并没有回收。


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org


[GitHub] [dubbo] hongyu-zxj commented on issue #9935: 2.7.10 大response >maxPayload 的异常情况下,出现内存泄露

Posted by GitBox <gi...@apache.org>.
hongyu-zxj commented on issue #9935:
URL: https://github.com/apache/dubbo/issues/9935#issuecomment-1123059409

   > 
   
   有空通过我上面上的方法进行复现吗?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org


[GitHub] [dubbo] chickenlj commented on issue #9935: 2.7.10 大response >maxPayload 的异常情况下,出现内存泄露

Posted by GitBox <gi...@apache.org>.
chickenlj commented on issue #9935:
URL: https://github.com/apache/dubbo/issues/9935#issuecomment-1120155318

   请提供一些jmap分析数据,以方便我们定位具体问题


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org


[GitHub] [dubbo] hongyu-zxj commented on issue #9935: 2.7.10 大response >maxPayload 的异常情况下,出现内存泄露

Posted by GitBox <gi...@apache.org>.
hongyu-zxj commented on issue #9935:
URL: https://github.com/apache/dubbo/issues/9935#issuecomment-1120169029

   > 可以复现一下,复现方法准备:本地通过visualvm 工具来监听 内存情况,先准备两个dubbo接口,一个是正常调用,一个是response大于maxPayload (**### 建议大于100M左右,太小的我也没有复现**)的异常接口;复现步骤:1、调用正常的dubbo接口,查看visualvm 的 byte[]内存情况和MySQLValueObject对象内存占比情况,接口正常返回后再点击visualvm的 perForm GC 触发full GC,再查看 byte[]内存情况和MySQLValueObject对象内存情况;会看到byte[]的内存占比基本恢复到调用前端的情况,MySQLValueObject 对象也消失回收了;2、调用准备好的异常接口,查看visualvm 的 byte[]内存情况和MySQLValueObject对象内存占比情况,可以看到这两项的内存都升高了,而且等接口正常返回了后,这两项的内存占比没有降下去,点击visualvm的 perForm GC 触发full GC后,这两项的内存占比依旧在,并没有回收。
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org