[jitsi-dev] Jitsi juses a LOT of memory on Mac


#1

Hello,

I am using Jitsi on an Intel Mac (2006) running Mac OS X 10.6.8. IT has 2GB of RAM. The java -version command yields:

java version “1.6.0_29”

Java™ SE Runtime Environment (build 1.6.0_29-b11-402-10M3527)

Java HotSpot™ Client VM (build 20.4-b02-402, mixed mode)

The version of Jitsi is  1.0-beta1-nightly.build.3820.

When I launch 

Jitsi and allow it to auto provision from my office, it is using ~ 308MB (it sets up for XMPP chat and SIP telephone protocols). If it stayed at that level, I could live with it. Then, I made phone call between jitsi and my cell phone. I do not remember which end initiated the call. When the call was complete, the Mac Activity monitor indicated that Jitsi was using almost 690MB of memory. I captured the logs (the zip is attached). Earlier, during a separate running of Jitsi, after two phone calls the memory usage was almost 1.2GB. The machine only has 2GB, so it means that I need to keep restarting the software.

Aside from this problem, it is a very useful piece of software!

If there is any more information that you require, please do not hesitate to send me an E-Mail requesting it.

Thanks,

Raymond Hendrey
4038 E. Wildcat Drive
Cave Creek, AZ 85331
Cell: 480.310.2572

2012-01-27@10.02.15-logs.zip (63 KB)


#2

Hello, Ray!

In order to start looking into the memory-related issue you've
reported, we'll need at least one Java heap dump from the Jitsi
process. A simple way to create a Java heap dump is by using Java
VisualVM which I think comes bundled with your version of the Java VM.
After Jitsi has acquired a lot of memory and while it is still
running, launch VisualVM, look at the Applications section, find Jitsi
(or its process id) listed under Local, right-click on it and choose
Heap Dump from the context menu. After the heap dump is ready in
Visual VM, save it into a file and send it to us. A Java heap dump
file is usually too big to send via e-mail so you may upload it
somewhere and just provide us the URL. Please note that the Java heap
dump may contain sensitive information so you may want to use
temporary account passwords in Jitsi while preparing the heap dump or
provide the heap dump to a limited number of Jitsi developers.

Regards,
Lyubomir Marinov