Comment #6 on issue 9005 by bre...@chromium.org: http://www.chromeexperiments.com/detail/monster/ crashses chrome when it finishes http://code.google.com/p/chromium/issues/detail?id=9005
The cause of the problem is in SkARGB32_Blitter::blitAntiH, we do: fDevice.getAddr32(799, -1); The -1 produces a coordinate above the bitmap. The cause of this is that "SkFDot6 y1" in do_anti_hairline is -476 = 0xfffffe25, which, when we convert to an actual pixel, is -1. The line being processed is a straight line from pt0 = (799.33374, 1.2360189) to pt1 = (808.49969, -7.4338055) -476 comes from pt1.y * 64 (in SkFDot6 format). The bounding box is the whole area which is 0,0,800,600, so there the start of the line is the edge of the screen. -- 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 -~----------~----~----~----~------~----~------~--~---
