Open
Bug 1926361
Opened 11 days ago
Updated 5 days ago
Potential memory leak in WebM Fuzzer
Categories
(Core :: Audio/Video, defect)
Core
Audio/Video
Tracking
()
NEW
People
(Reporter: jkratzer, Unassigned, NeedInfo)
Details
(Whiteboard: [fuzzblocker])
Attachments
(2 files)
It appears that the WebM media fuzzer is affected by a memory leak. We are regularly seeing OOMs from this fuzzer and they can only be reproduced by running multiple entries from the corpus.
To reproduce the OOM, download and unpack the testcase to the /corpora/
directory.
$ fuzzfetch --fuzzing --asan --target firefox common gtest xpcshell -n libfuzzer
$ FUZZER=MediaWebM ./libfuzzer/firefox -- -close_fd_mask=3 -detect_leaks=1 -malloc_limit_mb=5120 -max_len=102400 -rss_limit_mb=3500 -timeout=10 ./corpora/*
Reporter | ||
Comment 1•11 days ago
|
||
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Comment 5•9 days ago
|
||
This is impacting the performance of the fuzzer, please prioritize it appropriately.
Whiteboard: [fuzzblocker]
Updated•6 days ago
|
Severity: -- → S3
Updated•6 days ago
|
Flags: needinfo?(cchang)
Comment 6•5 days ago
|
||
This bug prevents fuzzing from making progress; however, it has low severity. It is important for fuzz blocker bugs to be addressed in a timely manner (see here why?).
:jimm, could you consider increasing the severity?
For more information, please visit BugBot documentation.
Flags: needinfo?(jmathies)
You need to log in
before you can comment on or make changes to this bug.
Description
•