Hi Salvatore,
So far, there has been no proof of a memory leak in the Akka Scheduler.
That code has not been touched since 2013, and is used by many in
production since version 2.2.0. While the lack of evidence is not evidence
of lack, I would like to see a convincing reproducer and data to
You can easily check what Roland suggested.
1. Setup the frequency of the scheduling to be very fast so memory will
grow quickly.
2. connect with visualvm\jconsole to the jvm and initiate gc manually.
3. Compare the trend of memory of the moments right *after the GC* and
see if
Hi Jeff,
I'm having the same problem. And I did the same, I was thinking it was my
application but is the Akka actors that use all the memory ... What can I
do?
Salvo
On Tuesday, 12 May 2015 07:02:51 UTC+1, Jeff Steinmetz wrote:
>
> I thought there was something specific I was doing wrong in
The same is upending to me. I should the system and restart it again
Did you have solve this problem? I have to realise my application soon and
I have this problem!!!
On Tuesday, 12 May 2015 07:02:51 UTC+1, Jeff Steinmetz wrote:
>
> I thought there was something specific I was doing wrong
