Re: [controller-dev] [mdsal-dev] Bug 7370 OOM due to suspected memory leak in akka.dispatch.Dispatcher found by hprof

I agree with Tom. Had experienced this earlier due to a laggard listener back before stable carbon cut. Eventually , listener had got fixed (not in connection with this observation but I had just picked up the build spaced well after the original build) and I had not been able to repro the

Re: [controller-dev] [mdsal-dev] Bug 7370 OOM due to suspected memory leak in akka.dispatch.Dispatcher found by hprof

yeah that looks like an issue. DeviceInitializationUtils is doing a blocking get on a Future which is usually not a good thing. And it occurred via an EOS data change and is blocking an akka Dispatcher thread. On a side note, there's a lot of threads with

Re: [controller-dev] [mdsal-dev] Bug 7370 OOM due to suspected memory leak in akka.dispatch.Dispatcher found by hprof

+openflowplugin-dev & +ovsdb-dev: Tom, On Mon, May 29, 2017 at 2:57 PM, Tom Pantelis wrote: Thanks a lot for replying, really appreciate it! It looks like the Dispatcher was for data change notifications. I suspect a > listener was hung or responding slowly so the

Re: [controller-dev] [mdsal-dev] Bug 7370 OOM due to suspected memory leak in akka.dispatch.Dispatcher found by hprof

It looks like the Dispatcher was for data change notifications. I suspect a listener was hung or responding slowly so the actor's mailbox filled up with change notifications. I would suggest getting a thread dump next time. On Mon, May 29, 2017 at 7:52 AM, Michael Vorburger