Comment #22 on issue 15577 by lafo...@chromium.org: Crash - tcmalloc::ThreadCache::Allocate(unsigned int) http://code.google.com/p/chromium/issues/detail?id=15577
I've been looking over our top allocation crasher and noticed a few things, which perhaps maybe unrelated but seem worthy of a closer look: 1.) We saw a big increase in the number of crashes related to allocate and the history db between 176 and 177 (r14339 and r14682 respectively), http://build.chromium.org/buildbot/perf/dashboard/ui/changelog.html? url=/trunk/src&range=14339:14682&mode=html 2.) Between those revisions an apparently significant change was made to the history db in r14609, http://src.chromium.org/viewvc/chrome?view=rev&revision=14609 Do you think these could be related? If so, how hard would it be to try and revert the r14609 changes? -- 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 -~----------~----~----~----~------~----~------~--~---
