[Bug 696770] Memory leak when processing h.264 field pictures

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Wed Jun 5 04:52:48 PDT 2013


https://bugzilla.gnome.org/show_bug.cgi?id=696770
  GStreamer | gst-libav | 1.0.5

--- Comment #18 from sreerenj <bsreerenj at gmail.com> 2013-06-05 11:52:44 UTC ---
(In reply to comment #17)
> (In reply to comment #15)
> > But we have to decode the fields individually. Which means considering each of
> > them as frames. Remember, this is only in case of filed-enocoded interlaced
> > content and not for interlaced frames.
> 
> Yes, but libav does not care if you pass two fields at once or just one. For
> other decoders that do care see bug #660770

aha, okay.

So you mean, the temporary fix would be to send only complete frame to
handle_frame() from base_decoder. right? But how can we make sure that the
frame is complete or not from basedecoder if there is no parser in the
pipeline? Only the individual decoders which are doing parsing themselves can
identify the frame boundaries. Am i missing something?

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.


More information about the gstreamer-bugs mailing list