GNOME Bugzilla – Bug 166073
[threads] wrong error handling
Last modified: 2005-02-08 14:04:44 UTC
GstThread will not revert its state on a failed parent state change return. This means that we lose thread references, which leads again to 100% CPU use. This easily reproduced by { fakesrc ! fakesink }, where fakesrc emits an error on NULL->READY, I can create a testcase if needed. Attached patch fixes this.
Created attachment 36878 [details] [review] crappy fix This fix was coded in less than a minute and shows how to solve it. Someone with more motivation may want to rewrite it to look better.
Thomas, I want to nominate this for a showstopped because the patch is very simple and straightforward, has little to no chance of breaking anything and fixes a very clear and simple issue (that is a daily practice in cupid). I'd appreciate this patch in 0.8.9.
ronald, any patch where - locks are involved - gotos are used - more than ten lines are touched are neither simple nor straightforward. I really don't know what to do with this. If this is considered a real blocker, we just have to start all over again, and we're screwing ourselves over again. and again.
K, skipping to 0.8.10 then.
Done.