Updates:
Status: Fixed
Comment #19 on issue 3795 by a...@chromium.org: Check:
CrashForBitmapAllocationfailure()
http://code.google.com/p/chromium/issues/detail?id=3795
Looks like we haven't seen this in a while so marking it as fixed.
--
You received this message because you are
Updates:
Labels: -Area-Misc
Comment #17 on issue 3795 by [EMAIL PROTECTED]: Check:
CrashForBitmapAllocationfailure()
http://code.google.com/p/chromium/issues/detail?id=3795
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or
Issue 3795: Check: CrashForBitmapAllocationfailure()
http://code.google.com/p/chromium/issues/detail?id=3795
Comment #16 by [EMAIL PROTECTED]:
Issue 1435 has been merged into this issue.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because
Issue 3795: Check: CrashForBitmapAllocationfailure()
http://code.google.com/p/chromium/issues/detail?id=3795
Comment #15 by [EMAIL PROTECTED]:
There are still cases where this crash can happen in theory. So I am
keeping it open
to see if we get more reports. If things are calm for a few weeks,
Issue 3795: Check: CrashForBitmapAllocationfailure()
http://code.google.com/p/chromium/issues/detail?id=3795
Comment #14 by [EMAIL PROTECTED]:
Amit, r5244 refers to this bug. Do you want to close it, or do you think
there's a
reason to keep it open?
--
You received this message because you
Issue 3795: Check: CrashForBitmapAllocationfailure()
http://code.google.com/p/chromium/issues/detail?id=3795
Comment #13 by [EMAIL PROTECTED]:
Another crash thread related to this bug.
The full crash report details can be found at:
Issue 3795: Check: CrashForBitmapAllocationfailure()
http://code.google.com/p/chromium/issues/detail?id=3795
Comment #12 by [EMAIL PROTECTED]:
Amit: how were you looking at the sizes? I found in the dump at the top of
the stack
where it CHECK(0)'s the sizes are off because they were in
Issue 3795: Check: CrashForBitmapAllocationfailure()
http://code.google.com/p/chromium/issues/detail?id=3795
Comment #9 by [EMAIL PROTECTED]:
My guess is that this is a general out of system memory error. The bitmap
bounds and
stack all look reasonable. Without a repro case, I don't think
Issue 3795: Check: CrashForBitmapAllocationfailure()
http://code.google.com/p/chromium/issues/detail?id=3795
Comment #10 by [EMAIL PROTECTED]:
OK, I don't see us doing anything fancy here for 1.0.
We can already see how often it happens, and it's one of the top crashes.
Do we have any other
Issue 3795: Check: CrashForBitmapAllocationfailure()
http://code.google.com/p/chromium/issues/detail?id=3795
Comment #7 by [EMAIL PROTECTED]:
None of the 3 stacks on this bug report are related to printing. In fact,
when
printing, no bitmap backend is created (otherwise it'd crash frequently
Issue 3795: Check: CrashForBitmapAllocationfailure()
http://code.google.com/p/chromium/issues/detail?id=3795
Comment #8 by [EMAIL PROTECTED]:
Slightly different stack, same line (CrashForBitmapAllocationFailure)
reportid=cf9fd94b09e40dacproduct=Chromeversion=0.3.154.9date=signature=RaiseExcep
Issue 3795: Check: CrashForBitmapAllocationfailure()
http://code.google.com/p/chromium/issues/detail?id=3795
Comment #6 by [EMAIL PROTECTED]:
I put all the conditions I could think abotu detecting into that function
already. If
we can think of more, I can add them there.
--
You received
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
Issue 3795: Check: CrashForBitmapAllocationfailure()
http://code.google.com/p/chromium/issues/detail?id=3795
Comment #3 by [EMAIL PROTECTED]:
Alin is correct, this is the fall through check @ line 126.
I wonder if this could be related to people using a default.dll (themes)
from a
previous
14 matches
Mail list logo
