Duncan Webb schreef: > I don't see how pylirc would have stopped the crashes when you are using > the event interface and was a bit surprised that this reduced the > occurrence of a crash.
Maybe it wasn't :/ Sometimes I get a crash at a point and when I try to redo it freevo won't crash, I will run for a couple of weeks with debug enabled, maybe something wil come out... > Rather than use the event interface, why don't you use the lirc > interface, it is much better tested. You need to use the dev/input > driver for lircd. > > I don't really see how to reproduce this error from the crash report. It > may be that the event interface is sending too many events too quickly > and the code does not have enough critical sections to prevent reentry. Actualy I used lirc at first instance but decided to step to event interface because it looks more proper. (less software needed, no extra daemon running and it's standard kernel stuff) Is there anyone else using the event interface and experiencing strange shutdowns? > It's not a problem, just that the sub-process has already died but > freevo thinks it is still running and it trying to kill it. This only > seems to happen after a crash. This also happens after a clean shutdown (freevo stop), I have to terminate the process with "kill -KILL $PID" p.s. Could problems have something to do with using Mplayer SVN? -- Groetjes Japie ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Freevo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-users
