[Webkit-unassigned] [Bug 12718] REGRESSION: Segmentation fault when loading abc.go.com
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Fri Feb 9 15:28:51 PST 2007
http://bugs.webkit.org/show_bug.cgi?id=12718
ddkilzer at webkit.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Segmentation fault when |REGRESSION: Segmentation
|loading abc.com |fault when loading
| |abc.go.com
Priority|P2 |P1
Keywords| |NeedsRadar, NeedsReduction,
| |Regression
Ever Confirmed|0 |1
Status|UNCONFIRMED |NEW
Severity|Blocker |Critical
------- Comment #1 from ddkilzer at webkit.org 2007-02-09 15:28 PDT -------
Confirmed with local debug build of WebKit r19537 with Safari 2.0.4 (419.3) on
Mac OS X 10.4.8 (8N1037).
The stack trace does not show WebKit in it, but loading this page does not fail
in shipping Safari. I suspect an over-released ObjC object.
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_INVALID_ADDRESS (0x0001) at 0xf3000e17
Thread 0 Crashed:
0 libobjc.A.dylib 0x90a564c7 objc_msgSend + 23
1 com.apple.Foundation 0x9265cea5
-[NSURLConnection(NSURLConnectionInternal) _sendCallbacks] + 748
2 com.apple.Foundation 0x9265cb41 _sendCallbacks + 201
3 com.apple.CoreFoundation 0x9082afd2 CFRunLoopRunSpecific + 1213
4 com.apple.CoreFoundation 0x9082ab0e CFRunLoopRunInMode + 61
5 com.apple.HIToolbox 0x92ddabef RunCurrentEventLoopInMode +
285
6 com.apple.HIToolbox 0x92dda2fd ReceiveNextEventCommon + 385
7 com.apple.HIToolbox 0x92dda154
BlockUntilNextEventMatchingListInMode + 81
8 com.apple.AppKit 0x9327f465 _DPSNextEvent + 572
9 com.apple.AppKit 0x9327f056 -[NSApplication
nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
10 com.apple.Safari 0x00006cea 0x1000 + 23786
11 com.apple.AppKit 0x93278ddb -[NSApplication run] + 512
12 com.apple.AppKit 0x9326cd2f NSApplicationMain + 573
13 com.apple.Safari 0x0005f54a 0x1000 + 386378
14 com.apple.Safari 0x0005f471 0x1000 + 386161
--
Configure bugmail: http://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