I have recently come accross with a possible memory leak on Jitsi,
which seemed very important. Its an issue about video streaming with
the client. I found out that some threads, which are created whilst
video preview is open in the Options->Video section, seem to be hung
up even if the video preview is stopped by closing the window or
changing to another tab in the Options menu. Each time I try to open
video preview tab in the options menu, new threads are created and
they never get destroyed until the client is totally shutdown by the
I tried to debug the problem through Eclipse IDE and saw that video
preview is triggered by some device capture code on Java side, and
with JNI, directshow interface for the Windows OS is accessed. I am
not so familiar with native side but what I can say is that, threads
are not destroyed after device capture code successfully calls doStop
and doDisconnect methods which access to directshow code on native
It seems that you are the author of the mentioned code in Java side
(DSCaptureDevice). Do you have an opinion on this? Is there a way to
detach those threads after we are done with video capturing?
I guess this is a major issue if the OS got overwhelmed with growing
number of directshow threads.
BTW, I ran the client on Windows XP SP3 machine and I used a Microsoft
Live Cam for video capturing.