Comment #12 on issue 133 by [email protected]: JSR-309 driver leaks
memory
https://code.google.com/p/mediaserver/issues/detail?id=133
Hi Waileong,
Yes, we did release media session before sending 200ok for BYE;
1)To identify the memory leak, made a test call & drop from phone without
any play.
The MediaGroup is not created in this scenario.
At the end of the call, after perform GC, the below objects retained in
heap...
-org.mobicents.fsm.Transition=24 instances
-org.mobicents.fsm.State=9 instances
-org.mobicents.fsm.FSM=1 instance
2)-The observation on your patch--#6..APR'15 2014--for the above call
scenario shows
-org.mobicents.fsm.State=3 instances
-org.mobicents.fsm.FSM=1 instance
--we observed delay before sending 200ok & got exception in while playing...
3)coming back to the point-1)...if we make 10 calls then
-org.mobicents.fsm.Transition=240 instances
-org.mobicents.fsm.State=90 instances..
-org.mobicents.fsm.FSM=10 instance..
after doing perform Gc the Transition comes down to 24, state=9, FSM=1
The fsm Transition objects created in NetworkConnectionImpl still remains
in heap.
Do you see this type of behavior for this test call, also tried with jsr309
sample PlayerServlet.java and found the same behavior.
4) How to check SipSessionBindingListener?
Regards & Thanks
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
---
You received this message because you are subscribed to the Google Groups "mobicents-all-issues-changes" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
