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 `GraphStage` which might show which streams stay open.
Johannes On Monday, September 25, 2017 at 10:39:01 AM UTC+2, Bartosz Jankiewicz wrote: > > 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.ActorCell. Along with > accompanying objects (scala.collection.immutable.RedBlackTree$BlackTree) > it saturated the heap. All ActorCell objects seem to be related to > Akka-Streams - their names are: StreamSupervisor-xxxxxx > > Has anyone fallen into a similar issue? > -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
