is still alive.
>
> Johannes
>
>
>
> On Tue, Sep 26, 2017 at 1:59 PM, Bartosz Jankiewicz <
> bartosz.jankiew...@gmail.com> wrote:
>
>> I have verified that but there are 2 places where declare the
>> materializers. Both are declared as vals. I will verify th
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
subclasses of `Actor` (which will probably be
> dominated by `ActorGraphInterpreter`) and once filtered by `GraphStage`
> which might show which streams stay open.
>
> Johannes
>
> On Monday, September 25, 2017 at 10:39:01 AM UTC+2, Bartosz Jankiewicz
> wrote:
>>
>>
ski
wrote:
> This code seems unlikely to be the cause, likely somewhere else - run your
> app while profiling to find the leak.
>
> On Mon, Sep 25, 2017 at 7:26 PM, Bartosz Jankiewicz <
> bartosz.jankiew...@gmail.com> wrote:
>
>> Indeed, this is what it looks like :)
>&
r stopped.
>
> —
> Konrad `kto.so` Malawski
> Akka <http://akka.io> @ Lightbend <http://lightbend.com>
>
> On 25 September 2017 at 17:38:57, Bartosz Jankiewicz (
> bartosz.j...@gmail.com ) wrote:
>
> I have been running an app with Akka Http 1.0.9.
>
>
I have been running an app with Akka Http 1.0.9.
It had only single endpoint respoding with JSON. The service returned the
value as future therefore I used onComlete semantics.
The app was consistently running into OoM issues. Heap dump analysis has
led me to 1,536,693 instances of akka.actor.A
