On Sep 26, 2009, at 10:39 AM, Harry Jordan wrote:
Wow. Thank you Bill. That's ore than I could have hoped for. You'r
right of course, there was some unexpected code getting loaded:
0x1d3000 - 0x1dbffc +com.sweetpproductions.SafariCookies 0.8 (0.8)
<9739F20D-A5C1-015A-FB1F-B0F66CD64AB9> /Library/InputManagers/Safari
Cookies/Safari Cookies.bundle/Contents/MacOS/Safari Cookies
Everything else except for this input manager seems quite standard,
so I suspect this could be the culprit. For now I'm going to wait
and see if I get any more crash reports in this vein before I
investigate any further.
... and people are upset by Input Managers getting the axe. ;)
Safari Cookies may or may not be to blame, but it is certainly
something that falls into the "unsupported hack" category and, thus,
is unsupportable.
Some developers have put checks into their app's startup that looks
through the list of +allFrameworks and +allBundles (see NSBundle) for
non-standard items, warning the user if certain things are found.
Generically overly defensive, but a good tactic if there is a
particular item that is causing problems.
In this case, it doesn't seem warranted in that Safari Cookies isn't
that widespread and it is only impacting the one user. If the user
can reproduce the problem, ask them to remove the Input Manager
(rename /Library/Input Managers/Safari Cookies is the easiest way) and
try again.
If it does reproduce, let me know as I would like to reproduce the
issue on my own machine and see if there isn't some way to harden the
collector against such defects, even if the answer is to detect and
warn.
b.bum
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
