Issue 3795: Check: CrashForBitmapAllocationfailure() http://code.google.com/p/chromium/issues/detail?id=3795
Comment #5 by [EMAIL PROTECTED]: The stack in comment 4 is actually at line 116 (a different bug, known cause): 113 : // If the bitmap is ginormous, then we probably can't allocate it. 114 : // We use 64M pixels = 256MB @ 4 bytes per pixel. 115 : const int64 kGinormousBitmapPxl = 64000000; 116 : CHECK(static_cast<int64>(w) * static_cast<int64>(h) < kGinormousBitmapPxl); See http://src.chromium.org/viewvc/chrome/branches/official/build_154.9/src/base/gfx/bitmap_platform_device_win.cc?view=annotate Brett: Is there anything we can do about the crashes at CHECK(0) at line 126? Marc-Antoine: Is there any chance this is printing related? Issue attribute updates: Status: Assigned Owner: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Labels: -Mstone-X Mstone-1.0 -- 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 -~----------~----~----~----~------~----~------~--~---
