Safari 5.1.7 Continues to Disappoint

[mnewman]

I'm just about to launch the latest release.

[mnewman]

I'm on Version 5.1.7 (7534.57.2, r119600)

I had my usual morning half a dozen tabs open when I clicked a link from MacInTouch. I had previously checked and all the tabs were fully loaded and looked OK. Immediately on clicking the link I got the "Web pages are not responding" message. What? They all responded perfectly. But, Safari forced me to load all of them again, so I had to sit and stare at a blank screen until all the pages loaded. From then on, every page had the annoying SPOD, even though the page was fully rendered.

Annoying, annoying, annoying.

[aehurst]

Safari is now a pain. Just switched to Chrome to get away from the seemingly constant server not responding mess followed by a lock up and the pinwheel of death.

[mnewman]

Except that for some people it seems to work just fine.

I'd like to figure out why....

[NaOH]

Quote: Originally Posted by mnewman Except that for some people it seems to work just fine. I'd like to figure out why....

I've generally been one of the lucky ones, but I'd also like to know what explains the discrepancies.

[mnewman]

I just installed Version 5.1.7 (7534.57.2, r121911).

Right clicking on any link causes WebKit to crash.

Clearing the cache causes the application to freeze, requiring a force quit.

WebProcess_2012-07-06-082309_Bleach.crash
WebProcess_2012-07-06-082344_Bleach.crash
WebProcess_2012-07-06-082353_Bleach.crash
WebProcess_2012-07-06-082403_Bleach.crash
WebProcess_2012-07-06-082412_Bleach.crash
WebProcess_2012-07-06-082424_Bleach.crash
WebProcess_2012-07-06-082432_Bleach.crash
WebProcess_2012-07-06-082717_Bleach.crash
WebProcess_2012-07-06-082732_Bleach.crash
WebProcess_2012-07-06-082859_Bleach.crash
WebProcess_2012-07-06-083021_Bleach.crash

[agentx]

Create a new users account and test.
Get rid of all Safari caches and com.apple.Safari from ~/Library/Preferences
Or completely reset Safari after backing up bookmarks if not on iCloud.
Make sure flash is up to date.

[mnewman]

I rolled back to the previous nightly (r121872) and all is well again.

Anyone else have trouble with r121911?

[benwiggy]

Quote: Originally Posted by mnewman I rolled back to the previous nightly (r121872) and all is well again. Anyone else have trouble with r121911?

I would suggest that you're more likely to have problems using nightly builds than with a release version direct from Apple.

I think if there was a general problem with 5.1.7 that caused this problem, there would be lots of threads about it and we would have seen a patch by now. Right-clicking on links works fine for me.

I would definitely test a new user account before leaping to the conclusion that it's the application code itself.

You've checked that any Extensions, plug-ins, or other software that might interfere with low-level stuff is not to blame?

[mnewman]

Well, I went to nightly builds based on a suggestion from another user here.

Whom should I believe?

[benwiggy]

Yes, I see that. It's not about believing one person or the other. It's about thinking through the problem.

1. The problems you are having are not universal, or even widespread. They seem particular to you.
2. Therefore, there are other things to rule out before concluding that it is the code of the app itself at fault.
3. Furthermore, nightly builds are likely to be less well-tested and possibly contain more or new errors.

You still haven't said whether you've tested the problem in a new user account, or indeed checked (or removed) any Extensions, Plug-ins, or third-party apps running in the background.
Posting an attachment of the text of the crash log might also be very useful.

[jamesandersen]

Quote: Originally Posted by mnewman Right. I guess I was especially frustrated last night because I lost so much writing. Grrrr. Plus, I had high hopes that the recent release would address the blank pages issue that seems to have plagues Safari for well over a year now. During last night's failure the infamous WebProcess shot up to 95% of cpu time. My wife doesn't use Safari at all any more. She does legal work here in Thailand and Safari simply will not open many of the sites she visits frequently; especially Thai government sites. She uses Chrome most of the time.

"Grrrr" is right, Newman, but I lucked out!

On trying to rescue my own typed text from a suddenly blank page, and after seeing that the SELECT ALL function was grayed out; unusable, I went back and forth from screen to screen while never closing my blank tab, but - admittedly - also not knowing what else I did. Then, while on the blank page, I checked the SELECT ALL function again and saw it was available!

So, I did SELECT ALL, then I clicked COPY, then did a PASTE into EVERNOTE, where all the text of the webpage I had "lost" magically appeared! One section of the page that scrolled; the section in which I had typed everything I could not afford to lose, was even there, and it was scrollable!

I then selected and copied what I needed to rescue, reloaded the page I had first typed my text into, pasted the text, then immediately saved that page like I should have done in the first lace. My data is now safe and sound.

Voila and Amen!