Comment #22 on issue 17569 by [email protected]: Crash in SkARGB32_Black_Blitter::blitMask http://code.google.com/p/chromium/issues/detail?id=17569
Adding new asserts and enabling asserts in Release builds yielded some good stack traces in these reliability runs: http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Reliability/builds/4 901/steps/reliability:%20partial%20result%20of%20current%20build/logs/stdio http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Reliability/builds/4 902/steps/reliability:%20partial%20result%20of%20current%20build/logs/stdio http://build.chromium.org/buildbot/waterfall/builders/Chromium%20Reliability/builds/4 903/steps/reliability:%20partial%20result%20of%20current%20build/logs/stdio -- 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 -~----------~----~----~----~------~----~------~--~---
