New submission from Uve Rick <[email protected]>: While doing test, I ran across a memory leak in the mpegts.c.
What I found was that more than one packet could be generated for each read. Since only the last packet is returned, the memory for the other generated packets would be lost. It is possible if a packet has a length of 0 and the next packet has a very short length on the same stream. A transport stream does not normally do this, but if the data is corrupt, it is possible. If you look at the code, new_pes_packet is called in three different places. It is possible to call it twice which results in memory loss. A patch was submitted to the devel list on 9/28/10 with the title: mpegts memory leak ---------- messages: 12078 priority: normal status: new substatus: new title: mpegts.c has possible memory leak type: bug ________________________________________________ FFmpeg issue tracker <[email protected]> <https://roundup.ffmpeg.org/issue2257> ________________________________________________
