Re: Memory leak found in java.util.concurrent.ForkJoinPool

2017-01-23 Thread Rory O'Donnell
On 21/01/2017 16:56, Mark Thomas wrote: On 21/01/2017 09:31, Konstantin Kolinko wrote: 2017-01-09 23:58 GMT+03:00 Mark Thomas : All, As a result of a thread on the users list, a memory leak has been discovered in java.util.concurrent.ForkJoinPool.commonPool. It appears that use of this pool

Re: Memory leak found in java.util.concurrent.ForkJoinPool

2017-01-21 Thread Mark Thomas
On 21/01/2017 09:31, Konstantin Kolinko wrote: > 2017-01-09 23:58 GMT+03:00 Mark Thomas : >> All, >> >> As a result of a thread on the users list, a memory leak has been >> discovered in java.util.concurrent.ForkJoinPool.commonPool. It appears >> that use of this pool is hard-coded in multiple plac

Re: Memory leak found in java.util.concurrent.ForkJoinPool

2017-01-21 Thread Konstantin Kolinko
2017-01-09 23:58 GMT+03:00 Mark Thomas : > All, > > As a result of a thread on the users list, a memory leak has been > discovered in java.util.concurrent.ForkJoinPool.commonPool. It appears > that use of this pool is hard-coded in multiple places such as > Collection.parallelStream().forEach(). >