Memor Leak in akka.dispatch.forkjoin.ForkJoinTask?

Akka
,
1

Hey,

I have a simple HTTP Application with a small in memory cache that fetches values from Redis. The amount of data promoted seems to slowly increase, where the survivor space becomes always full - the Yonge GC durations increases proportionally to a point where it is 100ms +. This happens with both CMS and G1.

At the same time, follow a heap dump, most of the memory (70%, 200mb) is consumed by akka.dispatch.forkjoin.ForkJoinTask, and I see the following large objects: (a) java.lang.ApplicationShutdownHooks.hooks, (b) java.lang.SecurityManager.rootGroup. Screenshots of object tree are attached

Granted, my Redis driver is somehow using 2000 threads, which is not how scala is intended to be used. https://github.com/scredis/scredis/issues/81

Screen Shot 2020-03-30 at 9.33.36 PM
Screen Shot 2020-03-30 at 9.33.36 PM2454×1156 259 KB

Screen Shot 2020-03-30 at 9.18.53 PM
Screen Shot 2020-03-30 at 9.18.53 PM2340×1008 165 KB

Screen Shot 2020-03-30 at 9.25.59 PM
Screen Shot 2020-03-30 at 9.25.59 PM2700×1794 480 KB

Screen Shot 2020-03-30 at 9.24.46 PM
Screen Shot 2020-03-30 at 9.24.46 PM2682×1650 430 KB

2

Do you start (and stop) many ActorSystem instances?

3

The Redis driver we were using was creating an ActorSystem per Redis node. We has a 30 node Redis cluster…
Fixing it to use one ActorSystem fixed it

Thanks!