Bug 134193 - getaddrinfo caching appears to leak large amounts of memory
Summary: getaddrinfo caching appears to leak large amounts of memory
Alias: None
Product: Fedora
Classification: Fedora
Component: glibc   
(Show other bugs)
Version: rawhide
Hardware: All Linux
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2004-09-30 03:19 UTC by Nicholas Miell
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version: 2.3.3-61
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-30 10:24:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Firefox backtrace (4.23 KB, text/plain)
2004-09-30 03:20 UTC, Nicholas Miell
no flags Details

Description Nicholas Miell 2004-09-30 03:19:31 UTC
Firefox has recently been prone to allocating multiple gigabytes of
memory and thrashing my box to death.

I tracked two problems back to gnome-vfs2, which have since been
fixed, but Firefox is still occasionally allocating huge chunks
amounts of memory.

The same update from rawhide which provided the buggy gnome-vfs2 also
came with the version of glibc where getaddrinfo caching was introduced.

I managed to accidentally trigger the bug in Firefox when running in a
debugger, and the only active thread was stopped in __nscd_getai, so I
think it's possible that the problem is in the getaddrinfo caching

This is on an AMD64 system, which may be related to the problem.

Comment 1 Nicholas Miell 2004-09-30 03:20:01 UTC
Created attachment 104562 [details]
Firefox backtrace

Comment 2 Nicholas Miell 2004-09-30 04:18:18 UTC
AFAICT, resultbuf is leaked if an intervening nscd GC causes
__nscd_getai to loop on retry.

Comment 3 Bill Nottingham 2004-09-30 04:46:57 UTC
This is with glibc-...-59?

Comment 4 Nicholas Miell 2004-09-30 04:56:29 UTC

Comment 5 Ulrich Drepper 2004-09-30 10:24:40 UTC
Should be fixed in 2.3.3-61.

Note You need to log in before you can comment on or make changes to this bug.