Updates:
Labels: -Mstone-2.0 -Pri-1 Mstone-X Pri-2
Comment #10 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
Talked to Mike about this. This is the failure of a static instance that
is always
256 bytes not being cleaned up properly when the thread goes away. We
would need a
whole lot of threads over a whole lot of time for this to be noticed. It
is not
clear how we would fix this. The memory is registered to be cleaned up on
thread
death -- it just doesn't happen.
Given his assessment I am reducing the priority and pushing this out for
reconsideration later.
--
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
-~----------~----~----~----~------~----~------~--~---
