Closed Bug 793608 Opened 11 years ago Closed 10 years ago

Valgrind on tbpl detects leak - PR_GetHostByName, PR_GetAddrInfoByName

Categories

(Core :: Networking, defect)

Product:
Core
Component:
Networking
Platform:
x86_64
Linux
Type:
defect
Priority:
Not set
Severity:
major

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: gkw, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: memory-leak, valgrind)

Attachments

(3 files, 1 obsolete file)

m-c changeset 555f91476597 Valgrind stack with line numbers
1.23 KB, text/plain
Details
m-c changeset 08d435dedc7f Valgrind stack with line numbers
853 bytes, text/plain
Details
m-c changeset df69d95f636c Valgrind stack with line numbers
2.00 KB, text/plain
Details
Attached file Valgrind stack (obsolete) — 
Valgrind detects a leak of 56 bytes (direct) with libresolv entries on the stack, see attached snippet which comes from:

https://tbpl.mozilla.org/php/getParsedLog.php?id=15471615&tree=Firefox

Guessing Core: XPCOM, please change component if necessary.
Summary: Valgrind on tbpl detects leak - 56 bytes are definitely lost (direct) with libresolv entries on the stack → Valgrind on tbpl detects leak - 56 bytes are definitely lost (direct) with libresolv / libc entries on the stack
Another similar stack, this time without libresolv, but otherwise still also involving libc on the stack.
Component: XPCOM → Networking
Summary: Valgrind on tbpl detects leak - 56 bytes are definitely lost (direct) with libresolv / libc entries on the stack → Valgrind on tbpl detects leak - PR_GetHostByName, PR_GetAddrInfoByName
This is no longer occurring in Valgrind-on-TBPL runs.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.