Re: [akka-user] Re: Akka Http memory leak suspect

2017-09-28 Thread Bartosz Jankiewicz
Hi Johannes, Thank you for looking into that. This is really surprising finding. I cannot find anything wrong with my code though in this regards. There is one more materializer beining initialized, but for an endpoint that is rarely used (Swagger docs - I have verified in the logs, that there ar

Re: [akka-user] Re: Akka Http memory leak suspect

2017-09-27 Thread Johannes Rudolph
Hi Bartosz, I had a quick look into the dump. It contains >317000 StreamSupervisors, so creating too many materializers is really the issue. Note, that the materializer itself might go out of scope but the engine still stays alive if the materializer has not been shutdown manually. I created http

Re: [akka-user] Re: Akka Http memory leak suspect

2017-09-26 Thread Bartosz Jankiewicz
I have verified that but there are 2 places where declare the materializers. Both are declared as vals. I will verify the number of materializer instances on my heap-dump to confirm. On Tue, 26 Sep 2017 at 13:24 Johannes Rudolph < johannes.rudo...@lightbend.com> wrote: > On Tue, Sep 26, 2017 at 7

Re: [akka-user] Re: Akka Http memory leak suspect

2017-09-26 Thread Johannes Rudolph
On Tue, Sep 26, 2017 at 7:18 AM, Patrik Nordwall wrote: > If the names are StreamSupervisor- I think it can be that a new > Materializer is created for each request. I don’t know if that is done by > your application or by Akka Http. Does that ring any bells? Do you have any > creation of stream

Re: [akka-user] Re: Akka Http memory leak suspect

2017-09-25 Thread Patrik Nordwall
If the names are StreamSupervisor- I think it can be that a new Materializer is created for each request. I don’t know if that is done by your application or by Akka Http. Does that ring any bells? Do you have any creation of stream materializers in your code? /Patrik mån 25 sep. 2017 kl. 21:51 sk

[akka-user] Re: Akka Http memory leak suspect

2017-09-25 Thread Bartosz Jankiewicz
Hi Johannes, I can share the heap dump. I will try uploading it to Google Drive. I'm still suspecting Akka Http. A few days ago I was forced to migrate to HTTP4S in emergency. After the migration of endpoints (no single other change applied) the heap dump utilisation is stable. Bartosz On Mon

[akka-user] Re: Akka Http memory leak suspect

2017-09-25 Thread johannes . rudolph
Hi Bartosz, I can look into the heap dump. You can send it to me privately. If that's not possible could you post an histogram? It would be great if that could be filtered once for subclasses of `Actor` (which will probably be dominated by `ActorGraphInterpreter`) and once filtered by `GraphSta