Safari 6 gets stuck; won't scroll or scrolls to show blank area

I've been having trouble with Safari 6 since upgrading to Mountain Lion several days ago. The symptom is that after using Safari for a while, I'll go to a Web site and the page will load, but it won't scroll. Sometimes when that happens I can't click on links or controls either. Other times, the page does scroll, but rather than show the rest of the page, Safari shows empty space of the page's background color. Refreshing the page doesn't help, nor does closing the window and visiting the URL again, but if I open a new tab or window and go to some completely different site, that page usually works okay. Once a site gets "stuck", I have to quit and restart Safari to get it to scroll again.


I've disabled all extensions and the problem still occurs. It's erratic, though, and seems to happen more frequently on some sites (metafilter.com) than others (cnn.com). It sometimes seems that opening a set of tabs (with "Open in Tabs") makes it more likely to happen.


I am working on a Web development project now, and am using Safari's JavaScript debugger and Web inspector frequently, if that might have something to do with it.


This is driving me nuts. It's disruptive to my development workflow, and I'd hate to have to turn to Chrome or Firefox for the work. Can anyone suggest some diagnostic tricks to try to figure out what's going on -- or, better yet, a solution?


Thanks!

Posted on Jul 29, 2012 12:39 PM

Reply
14 replies

Jul 31, 2012 6:15 AM in response to kbern

Thanks for the tip! I've also noticed the "break on uncaught exceptions" behavior, but didn't know it could be turned off. That thread was very helpful. Now that I know what to watch for, I'll try using Safari during development today, see if the problem goes away, and mark this question as "answered" if all is well. Thanks again!

Aug 3, 2012 7:51 AM in response to jgarbers

I'm experiencing the same behaviour without even opening the inspector.

On this page, for example, I couldn't copy/past the link of kbern because as soon as I tried to click the mouse in front of the text, the page zoomed back to the top of the posting.

Likewise trying to click the reply icon wouldn't work until I found that the "button" was at least 20 pixels below the text. Even then, trying to type in the editor sent me back to the top of the page.

I resorted to Chrome to enter this!

I've reset Safari 6. I've disabled extensions - including the developer menu. Sometimes the behaviour starts after a few seconds, other times I can work for a few hours before it hits.

Once it begins, it transfers to every open window/tab in Safari and I have no recourse but to quit.

Aug 3, 2012 8:14 AM in response to kbern

After a couple of days, I've found that as long as no script is paused, pages will load normally. That is, if I've hit a breakpoint in a particular page, other pages (especially ones I load after that) will not respond or render properly. But letting the script continue usually breaks the logjam, so to speak, and lets other pages work. It's odd that closing the page on a breakpoint doesn't "break the logjam".


In any case, the problem stands, but I have a workaround now. Thanks!

Aug 5, 2012 10:47 PM in response to kbern

@kbern, you can actually debug using Safari 6.0 inspector. Apparently following your link, it seems that on Safari 6.0, enables uncaught exceptions by default.


All you have to do is untick it for the pages to load properly. I have the same exact problem as jgarbers. I was wondering why everyone is saying safari 6.0 was so fast and smooth, while I'm having rendering problerms. Turns out not everyone opens the developer menu. Only people like us who work debugging pages use that.


So the solution, if you want the Developer Menu on always, you just untick the break on uncaught exceptions, and your pages should load properly.


Screenshot here:


User uploaded file

Aug 6, 2012 2:30 PM in response to kbern

on the same link you gave @kbern:


you said "Though that still doesn't solve the fact that I can't debug in Safari 6 at all."


So I thought you didn't know "uncheck all uncaught exceptions". Because if you did, you can debug in Safari 6.0. without any problems 🙂


@jmtl

- Regardless of closing, it still pause uncaught exceptions, its either you untick it based on the screenshot I provided. Or disable the web inspector completely, in Safari's Preferences > Advanced > Show Develop menu bar.

Aug 6, 2012 5:34 PM in response to chris.topher

Chris. We need to stop this "tit for tat"... you wrote:

"... Because if you did, you can debug in Safari 6.0. without any problems 🙂"

That's simply not true, Chris. Perhaps my setup is different than yours, but I stand by my statement: with those breakpoints unchecked, I still cannot debug in Safari. Period. Maybe you can, that's great. But the problem is, and the reason I posted, is that I can't. And I believe others can't. So we're looking for a solution to that problem.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Safari 6 gets stuck; won't scroll or scrolls to show blank area

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.