Comment #1 on issue 23081 by [email protected]: CachedResource memory leak in renderer http://code.google.com/p/chromium/issues/detail?id=23081
If the leak affects only the renderer process, and disappears along with the renderer's address space when it exits, then this seems mostly like a debugging issue, the leak checker reporting false positives. In that case, I would agree with (a), but conditionalize the call so it only happens in debug builds, so it doesn't slow down tab- closing in production. -- 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 -~----------~----~----~----~------~----~------~--~---
