Bug 54307 - setlocale leaks
Summary: setlocale leaks
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: glibc   
(Show other bugs)
Version: 7.1
Hardware: i386 Linux
medium
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Aaron Brown
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-10-04 05:05 UTC by David Baron
Modified: 2016-11-24 14:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-10-04 05:06:04 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
list of tops of stacks at which leaked memory was allocated (13.09 KB, text/plain)
2001-10-04 05:05 UTC, David Baron
no flags Details

Description David Baron 2001-10-04 05:05:02 UTC
Description of Problem:
  Looking at leak logs (based on overriding |malloc|, |realloc|, |calloc|,
and |free|) of running Mozilla, there are a bunch of leaks noticeable from
the glibc function |setlocale|.

Version-Release number of selected component (if applicable):
  glibc-2.2.2-10

How Reproducible:
  Well, the way I saw it is complicated, but one could presumably also
observe it by writing a tight loop to repeatedly call |setlocale|.

Additional Information:
  I'll attach to the bug a list of the lines at which the chunks of memory
leaked were allocated.  Note that Mozilla calls |setlocale| multiple times.
 Also note that while the line numbers and file names in the list of
tops-of-stacks are correct, the symbol names are incorrect.

Comment 1 David Baron 2001-10-04 05:05:59 UTC
Created attachment 33338 [details]
list of tops of stacks at which leaked memory was allocated

Comment 2 David Baron 2001-10-04 05:16:04 UTC
Actually, I think this bug is NOTABUG, since my for(;;) { setlocale(LC_ALL,
"C"); } didn't leak.  I'm not sure why I'm seeing what I'm seeing, though.

Sorry for the noise.  I should've tried that first.


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