[Webkit-unassigned] [Bug 11689] WebKit nightly crashes on launch

[bugzilla-daemon at webkit.org]

http://bugs.webkit.org/show_bug.cgi?id=11689





------- Comment #4 from llscotts at fastmail.fm  2006-11-25 08:41 PDT -------
When I attach the debugger to WebKit as it crashes, here is the output:

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Reading symbols for shared libraries ............ done
/Users/llscotts/21088: No such file or directory.
Attaching to program: `/Applications/Safari.app/Contents/MacOS/Safari', process
21088.
Reading symbols for shared libraries
.................................................................................................................................................................................
done
Reading symbols for shared libraries ............................ done
0x00328210 in -[WebFrame frameElement] ()

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x00000000
0x00328210 in -[WebFrame frameElement] ()
(gdb) 

Before disabling all InputManagers, I disabled each one mentioned in the
Console log as WebKit crashes, in the following order: SafariScript,
Creammonkey, Cocoa TextSelectionHelper, and Inquisitor.  Removing these doesn't
solve the problem, and WebKit crashes with the following statement in Console
log:
2006-11-25 11:27:11.751 WebKit[23322] Error swizzling
2006-11-25 11:27:11.751 WebKit[23322] Couldn't find orig
2006-11-25 11:27:11.751 WebKit[23322] Couldn't find alt
2006-11-25 11:27:11.751 WebKit[23322] Error swizzling
2006-11-25 11:27:11.751 WebKit[23322] Couldn't find orig
2006-11-25 11:27:11.751 WebKit[23322] Error swizzling
2006-11-25 11:27:11.751 WebKit[23322] Couldn't find orig
Nov 25 11:27:13 musicroom crashdump[23339]: Safari crashed
Nov 25 11:27:14 musicroom crashdump[23339]: crash report written to:
/Users/llscotts/Library/Logs/CrashReporter/Safari.crash.log

After this, I disabled InputManagers by renaming the folder, and WebKit runs. 
However, clearly there's something wrong with WebKit if you have to disable all
InputManagers in order for it to run.  It needs to be able to "survive" in the
real world...

Hope this helps... 

Leland

P.S. Remember, this error only cropped up after October 25.  Prior to that,
WebKit worked fine.  I think there may be a problem in the way WebKit is
disabling plugins it doesn't like as it launches.  Also, what is "swizzling"?


-- 
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.