Hello Roger, 2012/7/22 Roger Pack <[email protected]>: > Greetings fellow program(mers). > > A "situation" occurred the other day where, using (cross compiled) > ffmpeg+libx264 with mingw-w64, "--enable-pthreads" and the mingw-w64 > pthread library, some oddness would result, like the app would "hang" > eating up 100% cpu, seemingly doing nothing useful. I was told to > bring it up here, as well.
Well, the issue seems to be that a mutex, which is already up to be destroyed, is still waited to return. I allowed for this that a mutex can be destroyed even if another thread waits for lock for it. You may want to test revision 5250. > I attempted to capture stack traces during the time that it was "hung" > (though who knows how accurate they are): > https://gist.github.com/3125847 well, there isn't that much of information. Maybe you get more information by enabling WINPTHREAD_DBG define. > Anybody have any clue/idea as to what is going on? See above. Regards, Kai ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
