These leaks have always existed in the unit tests. They don't happen in
Chrome builds since the posted tasks always get a chance to run on different
thread where they clean up. But in unit tests that doesn't (always) happen.
It's been low priority for me to look at because it's not a real leak,
There's already this one that I know of:
http://code.google.com/p/chromium/issues/detail?id=20703, there may be
others.
On Thu, Sep 3, 2009 at 11:11 AM, Antony Sargent asarg...@google.com wrote:
In that case I think I'll just put a bug in for these and add a suppression
to get the tree green.
In that case I think I'll just put a bug in for these and add a suppression
to get the tree green.
Thanks.
On Thu, Sep 3, 2009 at 10:53 AM, John Abd-El-Malek j...@chromium.org wrote:
These leaks have always existed in the unit tests. They don't happen in
Chrome builds since the posted tasks
