Comment #9 on issue 8544 by nsylvain: Crash - SafeBrowsingResourceHandler::OnUrlCheckResult http://code.google.com/p/chromium/issues/detail?id=8544
There are plenty of PureCall crashes, but they come from all over the code base, not only SafeBrowsing. SafeBrowsing seems to have a bigger share of PureCall crashes though, so maybe something is wrong there. Paul should take a look at the crashes to make sure there is not something obvious there. As for the rest, we should start looking at them. Unfortunately PureCall crashes are often really hard to understand, and as Mal said, most of the time it's the result of a memory corruption, or using freed objects. I can investigate some tomorrow, but I would consider myself lucky if there is a fix that comes out of it. -- 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 -~----------~----~----~----~------~----~------~--~---
