Comment #16 on issue 17569 by [email protected]: Crash in SkARGB32_Black_Blitter::blitMask http://code.google.com/p/chromium/issues/detail?id=17569
This looks related, but since the other crash is in stack-allocated memory, the only way this corruption could have caused the other crash is if it were occurring simultaneously in a different thread. It's unlikely that heap corruption at this point could cause stack corruption in the other spot, since the clipRect was valid at the time that MaskSuperBlitter::CanHandleRect() was called, so it would have to have been corrupted CanHandleRect() was called. As another data point, it looks as if this crash has been happening sporadically for a long time (as far back as Chrome 1.0): http://crash/search?query=blitMask -- 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 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-bugs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/chromium-bugs?hl=en -~----------~----~----~----~------~----~------~--~---
