Bug 11851 – Webkit crashes when click on link to pdf file

• Component: Page Loading
• Status: RESOLVED DUPLICATE

[Patricia Warwick]

I tried to click on this link several times and each time I did Webkit crashed.

[Alexey Proskuryakov]

Please attach a complete crash log. Also, could you please tell what link you clicked on? Just opening the PDF document works fine for me.

[Patricia Warwick]

It crashed yesterday when I linked to the URL from a Google search window. It crashed a couple of times so I reported the crash. Sorry but I did not think to attach a crash log. I'll do so in future. However, when I attempted to recreate the problem today it did not crash.

[David Kilzer (:ddkilzer)]

(In reply to comment #2)
> It crashed yesterday when I linked to the URL from a Google search window. It
> crashed a couple of times so I reported the crash. Sorry but I did not think to
> attach a crash log. I'll do so in future. However, when I attempted to recreate
> the problem today it did not crash.

Crash logs are stored in your home directory here (even if you're using nightly WebKit builds on http://nightly.webkit.org/):

~/Library/Logs/CrashReporter/Safari.crash.log

They are concatenated to the end of the file as they happen.  You should be able to pull out the last one or two which would represent the PDF crashes (unless you had more crashes in the meantime).

Were you using a WebKit nightly build, or the shipping version of Safari?

[Patricia Warwick]

I had launched Webkit but because it shows Safari as the application name I must not have noticed that it had been running Safari at time of crash since when I looked at the Crash log and it shows the app as being Safari. 

I am attempting to use the Webkit but as you can tell I have not been paying sufficient attention to what was happening. Since both display the same About info is there another way of identifying the version I am using other than by using Command + Tab?

I've just changed my default browser to make it launch Webkit from now on. I have been installing the Nightly downloads.

Given this, is there any point in attaching the crash log?

[Alexey Proskuryakov]

(In reply to comment #4)
> I've just changed my default browser to make it launch Webkit from now on.

Please be advised that this is known to cause problems with RSS viewing.

> Given this, is there any point in attaching the crash log?

Yes - we'll be able to tell which version crashed. It's actually quite easy - in the module list at the end, there is a version of WebKit framework, and nightlies have 420+ there, e.g.:

  0x305000 -   0x416fff com.apple.WebKit 420+	/Users/ap/WebKit/WebKitBuild/Debug/WebKit.framework/Versions/A/WebKit

[David Kilzer (:ddkilzer)]

(In reply to comment #4)
> I had launched Webkit but because it shows Safari as the application name I
> must not have noticed that it had been running Safari at time of crash since
> when I looked at the Crash log and it shows the app as being Safari. 

When you launch a WebKit nightly, what you're really doing is launching the original Safari application that is installed on your Mac with a different WebKit framework library.  (Some "magic" is used to make it look like a different icon.)  That's why all of the crash logs appear in the Safari crash log file.

[Patricia Warwick]

Created attachment 11895 [details]
Safari Crash log

Here is the complete log.

[Patricia Warwick]

I've attached the log, but I'm not sure what link you are asking for ... the one I included when I created this bug is the one I clicked on. As I said then, it no longer crashes with that link. When it crashed, it did so before displaying the PDF file.

[David Kilzer (:ddkilzer)]

(In reply to comment #7)
> Created an attachment (id=11895) [edit]
> Safari Crash log
> 
> Here is the complete log.

I have no idea what's going on in the very last crash in the crash log on 12/17.  Is it off in a driver somewhere?

The two previous crashes on 12/16 both occur in "WebCore::NetscapePlugInStreamLoader::isDone() const" with what appears to be the Adobe Acrobat 7.0.8 plug-in installed and using WebKit r18244.  Looking at that method, I'm not sure how it could crash (unless we're not seeing the whole stack)?

Wow, the very first crash in the log is in Mac OS X 10.2.6 (build 6L60)!  :)

(In reply to comment #9)
> The two previous crashes on 12/16 both occur in
> "WebCore::NetscapePlugInStreamLoader::isDone() const" with what appears to be
> the Adobe Acrobat 7.0.8 plug-in installed and using WebKit r18244.  Looking at
> that method, I'm not sure how it could crash (unless we're not seeing the whole
> stack)?

That's bug 11430.

> 
> Wow, the very first crash in the log is in Mac OS X 10.2.6 (build 6L60)!  :)
> 

I'd call it a bug in Mac OS X that it doesn't purge old crash logs :-\

[David Kilzer (:ddkilzer)]

(In reply to comment #10)
> (In reply to comment #9)
> > The two previous crashes on 12/16 both occur in
> > "WebCore::NetscapePlugInStreamLoader::isDone() const" with what appears to be
> > the Adobe Acrobat 7.0.8 plug-in installed and using WebKit r18244.  Looking at
> > that method, I'm not sure how it could crash (unless we're not seeing the whole
> > stack)?
> 
> That's bug 11430.

Marking as duplicate.  Stack traces end (begin?) at the same method call.



*** This bug has been marked as a duplicate of 11430 ***