[Webkit-unassigned] [Bug 25055] New: Maximum sized canvas hangs/crashes Safari
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Apr 6 01:15:55 PDT 2009
https://bugs.webkit.org/show_bug.cgi?id=25055
Summary: Maximum sized canvas hangs/crashes Safari
Product: WebKit
Version: 528+ (Nightly build)
Platform: Macintosh
OS/Version: Mac OS X 10.5
Status: NEW
Severity: Normal
Priority: P1
Component: HTML DOM
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: eric at webkit.org
CC: mike at belshe.com
OtherBugsDependingO 23212
nThis:
Maximum sized canvas hangs/crashes Safari
I was trying to create a test case for bug 23212 and in doing so, I ended up
finding a related bug in our handling of large canvas sizes.
When running the attached test case, the following in spewed to the console:
Mon Apr 6 01:05:51 DumpRenderTree[2296] <Error>: CGBitmapContextCreateImage:
failed to allocate 1073741824 bytes.
Mon Apr 6 01:05:51 DumpRenderTree[2296] <Error>: CGImageCreate: invalid image
provider: NULL.
Mon Apr 6 01:05:51 DumpRenderTree[2296] <Error>: CGImageSourceGetStatusAtIndex
image source parameter is nil
Mon Apr 6 01:05:51 DumpRenderTree[2296] <Error>: CGImageSourceGetStatusAtIndex
image source parameter is nil
Mostly from under the BitmapImage::paint() method call.
Safari then hangs at 100% CPU (indefinitely, as far as I can tell) under:
940
-[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:]
940
-[NSView _drawRect:clip:]
940 -[NSScroller drawRect:]
940 -[NSScroller drawKnobSlotInRect:highlight:]
940 -[NSScroller _old_drawKnobSlotInRect:highlight:]
940 Draw3PartImage
940 _NSTileImageWithOperation
940 NSRectFillUsingOperation
940 CGContextFillRect
940 CGContextFillRects
940 ripc_DrawRects
940 ripc_Render
940 ripc_GetColor
940 ripl_Create
940 __spin_lock
940 __spin_lock
Probably CG has just been made unhappy at that point. ;)
P1 because this seems to be a reproducible hang/crash.
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
More information about the webkit-unassigned
mailing list