Open Bug 1441842 Opened 7 years ago Updated 2 years ago

Potential memory leak in media/libvpx/libvpx/vp8/vp8_cx_iface.c:594

Categories

(Core :: Audio/Video: Recording, defect, P3)

defect

Tracking

()

People

(Reporter: fan.gang.cn, Unassigned)

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36 Steps to reproduce: Scan Code with SourceBrella Pinpoint Actual results: File: media/libvpx/libvpx/vp8/vp8_cx_iface.c:594 The memory shared_mem_loc allocated on line 587 is leaked when the program takes the true branch on line 594. It is a rare case, but better fix it. I've uploaded a screenshot with source code and comments for a better description.
Based on the source code location, I believe this could start in Core::A/V in order to be further triaged.
Component: Untriaged → Audio/Video
Product: Firefox → Core
This is in upstream code I am not sure how easy it is to request a change.
Rank: 25
Component: Audio/Video → Audio/Video: Recording
Priority: -- → P3
Status: UNCONFIRMED → NEW
Ever confirmed: true
You should file this upstream really, https://www.webmproject.org/code/bug-reporting/ That said, when this leaks we're likely to OOM soon anyway, and that will take the process down. This is then pretty low prio.
Flags: needinfo?(fan.gang.cn)
(In reply to Andreas Pehrson [:pehrsons] from comment #3) > You should file this upstream really, > https://www.webmproject.org/code/bug-reporting/ > > That said, when this leaks we're likely to OOM soon anyway, and that will > take the process down. This is then pretty low prio. OK, thanks.
Flags: needinfo?(fan.gang.cn)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: