Problem: Sometimes Xfmedia hangs and cannot be closed with normal commands but only with killall. At the moment I have no reproducable examle, but it occures sometimes with streaming if something isn't correct One possibility to solve this would be a separate GUI thread or GUI process. Another (simpler) approach would be some kind of "Xine timeout" with alarm() or setitimer(). Reproducible: Always Steps to Reproduce: 1. 2. 3.
firstly, why is this marked enhancement? (In reply to comment #0) > Problem: Sometimes Xfmedia hangs and cannot be closed with normal commands but > only with killall. At the moment I have no reproducable examle, but it occures > sometimes with streaming if something isn't correct yeah, that's a pain, but i can't reproduce it myself, so it's not likely i'll be able to fix this. > One possibility to solve this would be a separate GUI thread or GUI process. > Another (simpler) approach would be some kind of "Xine timeout" with alarm() or > setitimer(). definitely not. this would introduce a lot of complexity and probably many more bugs. xine is designed to be called from the app's main thread (most of xine's actually work occurs in other threads). also, since alarm() and setitimer() use POSIX signals, this may not play nicely with xine's multithreaded/highly-mutexed nature. it's just not a very good solution, anyway. if there's a deadlock in xine's code, it's a xine bug and should be fixed. same with my code.
Ok, I didn't know that. If I have a reproducable case, I'll tell you.
I'd say that it's a xine problem. Mine does the same thing with every xine based app I run. It happens pretty randomly.
I don't think this is an issue anymore. Reopen if it can be reproduced reliably, and if other xine-based apps don't show the same problem with the same file.