Updates:
Summary: [MLK] TLS Callback not working properly and causing memory
leaks
Cc: [email protected] [email protected] [email protected]
[email protected]
Comment #3 on issue 6527 by [email protected]: [MLK] TLS Callback not
working properly and causing memory leaks
http://code.google.com/p/chromium/issues/detail?id=6527
This leak (along with a bunch of others with different stacks but all
leading to
ThreadLocalStorage) is being caused by TLS callback not working as
expected. It seems
even though the callback function (OnThreadExit) we define using some
pragma hacks,
gets called on every thread termination, the value of static variables (i.e.
tls_key_) is lost. So in ThreadExit() function there is nothing for us to
cleanup and
it returns without freeing the memory that it had allocated in Initialize()
method.
I do not understand TLS callback enough to know what the proper fix could
be so I am
just copying people who might know.
--
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
-~----------~----~----~----~------~----~------~--~---
