Page loading of most sites stalls on the first attempt. This includes the WebKit startup page. I have not pinned this problem down to a particular sequence or page Jim
Thanks for the bug report, Jim! Could you run the "sample" command again from a Terminal window when WebKit stalls and post the results to this bug? sample Safari 10 10 Do you see this on any particular web sites, or most of them?
Created attachment 16608 [details] Terminal screen.... Safari not found. The page that hung was the Webkit start up page. As soon as I double click the link address in the email for this page the Webkit startup page flashed up. Jim
Created attachment 16637 [details] Stall sample..... its an Apple site again.... There have been several sites that stall... This Apple site is dead stopped Jim
(In reply to comment #3) > Created an attachment (id=16637) [edit] > Stall sample..... its an Apple site again.... > > There have been several sites that stall... This Apple site is dead stopped Thanks for the sample, Jim! Which Apple web site were you visiting? What type of Mac is this happening on?
(In reply to comment #4) > What type of Mac is this happening on? Also, do you have the Safari 3 Public Beta installed? Thanks!
<rdar://problem/5539211>
Jim, I need more detailed information about this issue. Which WebKit nightly versions are affected? Which URLs (web pages) was Safari loading when you hit the issue? What hardware did you see this on? Which version of OS X are you using? And does this still happen?
Which WebKit nightly versions are affected? Sorry, not sure. It was about 6...builds back Which URLs (web pages) was Safari loading when you hit the issue? Seemed like most sights... Digg, Arstechnica etc the first time accessing the site, second time seemed to work as expected. What hardware did you see this on? MacBook Pro model MacBookPro2,1 Which version of OS X are you using? 10.4.10 And does this still happen? Have not seen the problem for the last 2..3 builds Thanks for all you do Jim
(In reply to comment #8) > And does this still happen? > Have not seen the problem for the last 2..3 builds Please reopen this bug if you see the behavior again. Thanks!