Summary: | crash + Safari extensions warning when none installed | ||
---|---|---|---|
Product: | WebKit | Reporter: | Ian Page-Echols <v8media> |
Component: | Page Loading | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Major | CC: | mrowe |
Priority: | P2 | ||
Version: | 523.x (Safari 3) | ||
Hardware: | Mac (PowerPC) | ||
OS: | OS X 10.4 |
Description
Ian Page-Echols
2007-05-14 16:02:42 PDT
(In reply to comment #0) > Current webkit from about 3:25pm today/Monday crashed and gives this message: > > Safari extensions were detected on your system. Extensions are incompatible > with nightly builds of WebKit, and may cause crashes or incorrect behavior. > Please disable them if you experience such behavior. > > No such extensions are installed, [...] This looks suspicious, and is probably the cause of the warning: 0x1956000 - 0x1958fff com.unsanity.menuextraenabler 1.0.3 /Library/InputManagers/Menu Extra Enabler/Menu Extra Enabler.bundle/Contents/MacOS/Menu Extra Enabler The next question is whether the warning is causing the crash, or if the crash is independent of the extensions issue. Please remove this extension and try to reproduce the issue. Please test the most recently nightly builds when filing obvious crashers like this. This was fixed in r21419 several days ago, and there have been at least 4 builds with the fix included. A "Safari extension" is any piece of executable code loaded into the Safari process via an unsupported mechanism. This includes input managers, APE haxies, and SIMBL plugins. There is no way to determine what such an extension will do once it has been loaded so the policy is that if we experience a crash, the user is asked to disable these extensions before reporting the bug so as to remove any blame from these unsupported extension mechanisms. The code that detects such extensions is very trivial, and it is rather unlikely it would be to blame for any crashes. *** This bug has been marked as a duplicate of 13660 *** |