3 Replies Latest reply: Jun 24, 2010 3:18 AM by Kevin McMurtrie
Bubba_the_Programmer Level 1 Level 1 (0 points)
I hate to simply toss out YAS5CR (Yet Another Safari 5 Crash Report) but I've done some investigation which hopefully will shed light on at least one of its numerous shortcomings.

I attached Visual Studio to Safari.exe and loaded a page that it was crashing on. This generated an exception ("Unhandled exception at 0x015dd9a7 in Safari.exe: 0xC000005: Access violation reading location 0x00000808"). The call stack is below. I know that's not likely of much interest to the "users" reading this, but if there's a Safari engineer who happens by, maybe it means something to them.

I work on a team that develops web pages and we've found a handful that cause Safari 5 to crash. On Mac, too, so we can't place the blame in Redmond.

The other problem I've observed (on one machine) is that typing the first character into the URL bar hangs Safari5 for 20-30 seconds. It then proceeds normally (until I get to a page that crashes it).

My theory is that there are at least two bugs:
- In its zeal to make JS run fast, it appears to run "too fast" and crashes. This is both an annoyance and a serious bug (IMHO); it's a small leap from a crash to a buffer overrun security exploit. You know; the kind of thing IE used to be renowned for.
- There's some new(?) Chrome-esque history lookup going on as one types in the and sometimes this goes south, causing delays or crashes (see many reports elsewhere).

I'd wager that some people reporting crashing at startup likely have a home page that is hitting the first of these issues (I was in that camp). I found I could launch Safari from the command line by typing something like: "c:\Program Files\Safari\Safari.exe about:blank". So long I as don't visit the wrong page, it works Ok (aside from the hang when I type in the url bar).

Regards. I'm off to pursue a fix in the Webkit developer world, if I can find my way there...

JavaScriptCore.dll!015dd9a7()

[Frames below may be incorrect and/or missing, no symbols loaded for JavaScriptCore.dll]
JavaScriptCore.dll!01601d31()
JavaScriptCore.dll!015e15fc()
JavaScriptCore.dll!015e56a6()
JavaScriptCore.dll!015d1fb1()
JavaScriptCore.dll!0160b900()
JavaScriptCore.dll!015d81f2()
JavaScriptCore.dll!015d81f2()
WebKit.dll!0238e554()
JavaScriptCore.dll!015d81f2()
WebKit.dll!023aba4f()
WebKit.dll!02034b8f()
JavaScriptCore.dll!0160b900()
WebKit.dll!0231fffc()
WebKit.dll!02368abc()
Safari.dll!01013580()
JavaScriptCore.dll!0160b900()
WebKit.dll!023bd9b1()
WebKit.dll!023bd977()
WebKit.dll!023bc6b9()
WebKit.dll!0247d66b()
WebKit.dll!023d62e7()
WebKit.dll!020cb225()
CFNetwork.dll!0179b996()
CFNetwork.dll!0179bcf9()
CoreFoundation.dll!012a506c()
CoreFoundation.dll!0132aae4()
CoreFoundation.dll!012db080()
CoreFoundation.dll!0132aae4()
CoreFoundation.dll!012db344()
CFNetwork.dll!0179cb79()
CFNetwork.dll!0179bf7f()
user32.dll!7e418734()
user32.dll!7e418816()
user32.dll!7e4189cd()
user32.dll!7e418a10()
Safari.dll!00baae72()
user32.dll!7e418734()
user32.dll!7e418bd9()
user32.dll!7e41885a()
user32.dll!7e428ea0()
user32.dll!7e428efc()
ntdll.dll!7c90e473()
user32.dll!7e429950()
Safari.dll!00b519c9()
Safari.dll!00b98dc6()
Safari.dll!00b500bc()
Safari.dll!00b4ba13()
Safari.dll!00baba8b()
Safari.dll!00bac198()
Safari.exe!00401457()
msvcr80.dll!78136d63()
msvcr80.dll!78134c39()
msvcr80.dll!78133760()
msvcr80.dll!78131d17()
Safari.exe!004014b6()
Safari.exe!0040161b()
kernel32.dll!7c817077()
Safari.exe!00620069()
Safari.exe!00620075()
Safari.exe!0061004d()
Safari.exe!0061004d()
Safari.exe!0061004d()

Internet, The network is the computer, or something like that.
  • b noir Level 9 Level 9 (72,015 points)
    The call stack is below. I know that's not likely of much interest to the "users" reading this, but if there's a Safari engineer who happens by, maybe it means something to them.


    Good catch, Bubba!

    If you've got the time, could you put through a bug report to Apple for that one?

    If you want to track the bug, the best way to do that is to register (free) as an Apple Developer:

    [Register as an Apple Developer|https://swdlp.apple.com/cgi-bin/WebObjects/SoftwareDownloadApp.woa/18 32/wo/ghc5q6Ft5BfSvqaLsj00wg/2.5]

    ... and then you can use the Apple Bug Reporter to submit the bug:

    [Apple Bug Reporter|https://swdlp.apple.com/cgi-bin/WebObjects/SoftwareDownloadApp.woa/183 2/wo/ghc5q6Ft5BfSvqaLsj00wg/2.5]
  • Reverse_Parn Level 2 Level 2 (210 points)
    It's your PC. I can't replicate this issue on my test PCs. I am running VS2008.

    Can you provide a URL that you visit before this occurs? I can type all day in my URL bar and it doesn't crash.

    Usually the error point to the incorrect memory location is driver related, but it could be the software that interfaces with your driver. Driver could be a memory manager, hardware driver, etc.

    If I can replicate that error, I'd like to see it. Post instructions and I'll try it out.
  • Kevin McMurtrie Level 1 Level 1 (0 points)
    Any Shutterfly personal share site has about a 9 in 10 chance of crashing if Safari is in the foreground as the page loads.
    http://asdf.shutterfly.com