Comment #8 on issue 27936 by [email protected]: Leak in
history::ExpireHistoryBackend::BroadcastDeleteNotifications
http://code.google.com/p/chromium/issues/detail?id=27936
What were the commits in the blamelist? I can't see them or the stdio
anymore, that
bot link is too old.
It looks from the errors above like there was a leak when running the
ExpireHistoryTest unittests. ExpireHistoryTest::BroadcastNotifications()
takes
ownership of the pointer that claims to be leaked above, and frees it during
TearDown(). Perhaps the test segfaulted or something else that avoided
TearDown(),
triggering a leak? If so, this would be a transient failure. I don't know
if there
are more robust ways to write the unittest code.
--
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
