GNOME Bugzilla – Bug 787869
audiovisualizer: mutex unlock added in error case
Last modified: 2018-11-03 11:59:44 UTC
Created attachment 360023 [details] attached patch Hi, In gst_audio_visualizer_chain function. Jumps out of a held mutex without unlocking it. if (!klass->render (scope, inbuf, &outframe)) { ret = GST_FLOW_ERROR; gst_video_frame_unmap (&outframe); goto beach;
Thanks for the patch. This is formally correct of course. I wonder what exactly config_lock protects though (if it's needed), and if it should be held during the call into the subclass at all.
Can you please commit if patch is correct.
First the context / meaning of that mutex has to be understood, maybe the mutex shouldn't be taken at all here.
Ponnam, do you want to do some research on that?
mutex should be unlock when it goes in error case.
Yes but that's beside the point. Should it be locked at all here when calling into the subclass, what exactly is it protecting and why?
yes your right. will do some research
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-base/issues/381.