Postby Rémi Denis-Courmont » 17 Feb 2010 19:16
It should be pretty obvious from the stack trace if the deadlock occurs in LibVLC.
There have been some deadlock bugs in LibVLC. But in many cases, the problem was the application not handling LibVLC events properly, and then deadlocking itself. Do note that events are delivered from LibVLC threads, not from your application event loop.
Rémi Denis-Courmont
https://www.remlab.net/
Private messages soliciting support will be systematically discarded