Re: RFR: 8255694: memory leak in JDWP debug agent after calling JVMTI GetAllThreads [v2]

2020-11-02 Thread Chris Plummer
> The debug agent needs to deallocate memory that is allocated by calls to > GetAllThreads. There were two places were this was not being done, resulting > in a memory leak. Chris Plummer has updated the pull request incrementally with one additional commit since the last revision: Remove un

Re: RFR: 8255694: memory leak in JDWP debug agent after calling JVMTI GetAllThreads

2020-10-31 Thread Serguei Spitsyn
On Fri, 30 Oct 2020 20:30:49 GMT, Chris Plummer wrote: > The debug agent needs to deallocate memory that is allocated by calls to > GetAllThreads. There were two places were this was not being done, resulting > in a memory leak. This looks good. Nit: semicolon sign can be removed: err: ;

Re: RFR: 8255694: memory leak in JDWP debug agent after calling JVMTI GetAllThreads

2020-10-30 Thread Alex Menkov
On Fri, 30 Oct 2020 20:30:49 GMT, Chris Plummer wrote: > The debug agent needs to deallocate memory that is allocated by calls to > GetAllThreads. There were two places were this was not being done, resulting > in a memory leak. Marked as reviewed by amenkov (Reviewer). - PR: htt

RFR: 8255694: memory leak in JDWP debug agent after calling JVMTI GetAllThreads

2020-10-30 Thread Chris Plummer
The debug agent needs to deallocate memory that is allocated by calls to GetAllThreads. There were two places were this was not being done, resulting in a memory leak. - Commit messages: - Make sure to deallocate jthread array allocated by GetAllThreads. Changes: https://git.openj