Updates:
Owner: [email protected]
Cc: [email protected]
Comment #6 on issue 9369 by [email protected]: Mem leak in net_unittests
- ProxyScriptFetcherTest.HttpMimeType
http://code.google.com/p/chromium/issues/detail?id=9369
This looks bogus.
The leak being shown is a block of memory allocated internally by the
setenv()
library call.
The values passed into setenv() are fine, and do get cleaned up.
I believe this is just a false-positive of the tool. Since environment
variables last
the duration of the process, I wouldn't be surprised if the library leaks
these
values intentionally.
> This same test is run on the Windows purify bots, and I don't think it
> shows as a leak.
True, however strictly speaking the Windows bot is taking a different code
path (this
is leak from POSIX-specific code path).
@nirnimesh: Assigning back to you.
I recommend testing on Linux Valgrind. If it doesn't show as error there,
then we
should open a bug on mac Valgrind. And if it does show as an error, then we
should
add it to our whitelist.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
