If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Small leak under SECITEM_AllocItem_Util

RESOLVED INCOMPLETE

Status

NSS
Libraries
RESOLVED INCOMPLETE
3 years ago
2 years ago

People

(Reporter: mccr8, Assigned: Wan-Teh Chang)

Tracking

(Blocks: 1 bug, {mlk})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
Direct leak of 24 byte(s) in 1 object(s) allocated from:
    #0 0x471e51 in calloc /builds/slave/moz-toolchain/src/llvm/projects/compiler-rt/lib/asan/asan_malloc_linux.cc:90
    #1 0x7f2f3c5612a7 in PORT_ZAlloc_Util /builds/slave/try-l64-asan-00000000000000000/build/security/nss/lib/util/secport.c:117
    #2 0x7f2f3c55d4cf in SECITEM_AllocItem_Util /builds/slave/try-l64-asan-00000000000000000/build/security/nss/lib/util/secitem.c:28
    #3 0x7f2f29b87ef7 in ffi_call_unix64 (/builds/slave/test/build/application/firefox/libxul.so+0x9908ef7)

I'm seeing this with LSAN runs of bc1 and bc3.  Unfortunately, the stack is not useful.  I'll have to try running these locally in the hopes of getting more information.
(Assignee)

Comment 1

3 years ago
Andrew: Thanks for the bug report. Without knowing where that
SECITEM_AllocItem_Util call is (in the source code it is
often a call to the SECITEM_AllocItem macro), we can't
investigate this memory leak.
Assignee: nobody → wtc
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX

Updated

2 years ago
Resolution: WONTFIX → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.