I also tested some video call with the client and I see the same
problem there. What is the current status in the fix? Is there any
updates? Does detaching the threads on device stopping work?
On Thu, Mar 31, 2011 at 11:46 AM, Sebastien Vincent <firstname.lastname@example.org> wrote:
Le 31/03/11 10:25, Lyubomir Marinov a écrit :
On Thu, Mar 31, 2011 at 11:18 AM, Sebastien Vincent >> <email@example.com> wrote:
The directshow native code use AttachCurrentThreadAsDaemon and does not
DetachCurrentThread after so the daemon thread stay.
As far as my experience goes, AttachCurrentThreadAsDaemon does not
prevent the native thread from perishing. Is it not correct?
Maybe it is an internal directshow thread that never die. I will try to find
some information about that.
If the native thread calls back to you and you
AttachCurrentThreadAsDaemon when you enter the callback and
DetachCurrentThread when you exit the callback, there is a performance
downside that each time the callback is executed a new Java Thread
object has to be created. And in the case of capturing with a
callback, one may pretty much create such Java Thread objects in the
range of hundreds in a very short time.
OK, I will modify code to just call DetachCurrentThread when the capture