This site is for data and figures of the paper SMOKE.
Comment #5 on issue ## by bugdroid1@chromium.org: A memory leak in handler-outside.cc:158
The following revision refers to this bug:
commit hidden-for-review
Date: Wed Feb 21 00:15:19 2018[wasm] [trap handler] do not leak memory on failure path
There were two failure paths where the CodeProtectionInfo object would not be
freed. This adds a free() on those paths to prevent a memory leak.
Actual results:
File: dom/media/encoder/VP8TrackEncoder.cpp:254
videoData allocated on line 279 is not freed when the function returns on line 286/293/300/306. Since videodata is considered a big data, it may cause severe memory leaks.
I've uploaded a screenshot with source code and comments for a better description.
>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.
>Actual results:
File mozilla-unified/media/mtransport/nr_timer.cpp:216
The allocated variable callback on line 210 is leaked when the program returns on line 217.
I've uploaded a screenshot with source code and comments for a better description.
Actual results:
The memory allocated by strdup(appEnv) on line 179 is never freed in the program.
File: browser/app/nsBrowserApp.cpp:179
Actual results:
"adapter" allocated on line 603 is leaked when mGMPLoader->load returns false on line 606.
File: dom/media/gmp/GMPChild.cpp:555
Expected results:
delete adapter before exiting.
Actual results:
File mozilla-unified/media/mtransport/nr_timer.cpp:216
The allocated variable callback on line 210 is leaked when the program returns on line 217.
I've uploaded a screenshot with source code and comments for a better description.
1/4 Comment: Closes #17033, #17032, #17031, thanks @fangang190
Im not sure about right way to fix for #17030, cuz im not an expert in android apk, and calling zipClose(unaligned_apk, NULL); before return may cause errors, so anybody with free time and knowledge could fix it instead
3/4 Comment: Closes #17033, #17032, #17031, thanks @fangang190
Im not sure about right way to fix for #17030, cuz im not an expert in android apk, and calling zipClose(unaligned_apk, NULL); before return may cause errors, so anybody with free time and knowledge could fix it instead
4/4 Comment: Closes #17033, #17032, #17031, thanks @fangang190
Im not sure about right way to fix for #17030, cuz im not an expert in android apk, and calling zipClose(unaligned_apk, NULL); before return may cause errors, so anybody with free time and knowledge could fix it instead
2/4 Comment: Closes #17033, #17032, #17031, thanks @fangang190
Im not sure about right way to fix for #17030, cuz im not an expert in android apk, and calling zipClose(unaligned_apk, NULL); before return may cause errors, so anybody with free time and knowledge could fix it instead
Comment: looks like a non-issue, since those returns end up exiting the process. I've fixed them anyway.
Comment: fixed in next. another non-issue, since that code is only executed from a specific test or two, and executes once in startup.
>There is a potential memory leak defect in mysql-server-mysql-5.5.51/cmd-line-utils/libedit/np/vis.c:436.
The memory allocated on line 420 is assigned to variable nextra. It is not freed when this function returns to its caller on line 436.
It is freed on line 439, which implies the developer award the necessity of freeing this memory. The leak on line 436 might be a mistake.
This report is similar to https://bugs.mysql.com/bug.php?id=89797&thanks=4.
We find a memory leak bug in apps/s_server.c 3294 (3330 in the most recent version). The variable con is not released when taking the "err" goto statement at line 3305.
We find a memory leak bug in ssl/s3_lib.c 4554 (4606 in current version).
This bug happens when the program taking true branch at line 4569 and goto the err label.There is no free operation in the err section.
It happens at line 2923 ( 2961 in the current version). Leaks when going to the err label.
the early return of return TEE_ERROR_BAD_STATE; at line 380 will leak the memory block pointed by dir (line 364)
cdata leaks when job_run fails. I've checked the code of job_run, it does not free cdata when fails.
Description:
Same problem as above in cmd-if-shell.c
"found" is leaked when format_choose failed.
The pointers nodes in the code point to two newly-allocated memory. If rc < 0 in the code happens, it will go to the label fail, where nodes are not released.
The pointers nodes6 in the code point to two newly-allocated memory. If rc < 0 in the code happens, it will go to the label fail, where nodes6 are not released.
It has been confirmed first, but later being classified as unconfirmed since it happens in main.
We classify this one as confirmed since it has been confirmed by at least one developer.
We find a memory leak defect in the file tools/wrc/wrc.c.
I've uploaded a screenshot of the leak trace.