On 11 October 2013 10:53, Sven Van Caekenberghe <sven@stfx.eu> wrote:

On 11 Oct 2013, at 10:24, Norbert Hartl <norbert@hartl.name> wrote:

> I can report that the behavior is different now. There were two new vm releases this week in ppa. The first one didn't work but the second changed something. My application was never running that long. It is more than a day now having an actual external objects table size of 623 which wasn't ever reached before. So I would say that there is chance that this particular problem is gone. I monitor this further and I think that this wasn't the only problem. But then it is another problem.

Yeah, but not knowing your application load, 623, which would be about 200 sockets (3 semaphores per sockets), is still a lot to be active at the same time. Can you in some way invoke a full GC externally, like using ZnReadEvalPrintDelegate and see if it eventually drops due to finalization ? It should, at least that is what I see.


yes, 600 semaphores indicating there are a possibly leak somewhere.
��
> Thanks to all of you who've helped solving this. If it comes to the VM being the source of problems it is always extra annoying because it is way harder to change something there.
>
> Norbert
>



--
Best regards,
Igor Stasenko.