https://bz.apache.org/bugzilla/show_bug.cgi?id=60620
Mark Thomas changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
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
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
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().
>
https://bz.apache.org/bugzilla/show_bug.cgi?id=60620
Konstantin Kolinko changed:
What|Removed |Added
Component|Catalina|Catalina
Target Milestone|-
https://bz.apache.org/bugzilla/show_bug.cgi?id=60620
Konstantin Kolinko changed:
What|Removed |Added
OS||All
--- Comment #1 from Konstanti
https://bz.apache.org/bugzilla/show_bug.cgi?id=60620
Bug ID: 60620
Summary: [JRE] Memory leak found in
java.util.concurrent.ForkJoinPool
Product: Tomcat 9
Version: 9.0.0.M15
Hardware: PC
Status: NEW
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().
I have some ideas about how to work-around the leaks
