Q: safari rendering issues

Mid 2009 17" MBPro. OS 10.7.5 Safari 6.0.2 (7536.26.17)

Same problems. Became especially bad today, including my own home page which recently worked. Frequently graphics aren't display. One website using tables has black text on black background. Another site white text on white bg.

Really bad news. Have to switch default to FireFox for awhile as every site that's bad on Safari works fine on FireFox.

It looks like a fix is coming soon! I just tested the latest Nightly build of Webkit and I'm not having the weird issues, and my scrolling performance is drastically improved. Give it a whirl! http://nightly.webkit.org

I'm seeing the same issues as before running the latest Webkit nighly builds :/

This is disappointing

I had heard the news of the latest webkit nightly fixing scrolling speed on retina MBPs and sure enough, the difference is incredible. I switched back from Chrome hoping that I would also see this issue go away. I haven't seen it yet, but if you've seen it then I'm sure it'll come around eventually.

Chrome is a fine browser and all, but Safari just feels right. I need Safari back. Please, Apple.

I can confirm that in the latest WebKit nightly I am again having the same issues now with rendering. Text flashes and blinks inside of text boxes, "pop-up" type elements don't appear correctly, animated GIFs seem to skip around in their frames.

Still having the same rendering issues since the release of Mountain Lion.  Worse than that is that Safari's memory leaks also seem to be getting worse, as today there was so much swapping going on that my computer went back to sleep before I could type the password after resuming.  The only thing that still keeps Safari usable to me is the Javascript Blocker add-on, but even then I'm still restarting it on a daily basis due to the memory leaks.

I am having the same problems with Gmail rendering in Safari. I have Safari 6.0.2, running on brand new MacBook Pro (non-retina).

Just found this on support:

https://discussions.apple.com/message/19159849#19159849

I deleted cache.db and it seems to be working.

Could you report if you were having the issues on any sites other than Gmail?

In my testing, it seems like a 'fresh' browser (for example, after installing the webkit nightly) seems to work for a day or two before it starts acting up. I wonder then, does the cache.db file need to be deleted once every day or two when its acting up for this to remain not a problem? Or does that user suggest that deleting the cache.db once will solve the problem permanently? I've had it on several different machines now/clean installs.

I just tried deleting cache.db (180 MB, not sure if that's large?) but it doesn't look to have solved the issue. Still seeing text-input rendering issues (among others but they seem to be the most common).

@inc3pt I don't use the Gmail web interface, I'm seeing this issues everywhere.

I've only noticed it in Gmail.

I did the cache.db and it seemed to work. But I went to something else, came back, and the problem was back.

Apple needs to understand, before we need more ways to share the webpages we're reading, before we need better integration with other iDevices, before we need smaller iPads (or bigger iPhones depending on how you look at it), the first thing we need is for the basic things to work.

This bug affects every single Mac user in my office (except those who long ago switched to FF/Chrome). I would like to think that Apple is well aware of the issue and is putting forth every possible bit of effort, retasking programmers to make sure that full attention is devoted to the most annoying ML issue by far.

Please, please... before all else, just make my **** Safari work.

I've been noticing this problem for a while, especially with Google Reader. I switched to chrome for a while, hoping this bug would be resolved, but months later it's still an issue. Very frustrating.

I've been trying an experiment related to deleting the cache.db file.

It's not exactly scientific but everytime it starts acting up and I see some rendering errors, I close Safari, delete the cache.db, and open Safari again. Immediately the problem goes away and seems to stay away for 24-48 hours.

I can't quite confirm yet, but usually if I "just" restart Safari without deleting the cache.db, the rendering errors seem to come back sooner.

Well, I've given up. This problem has persisted since the release of Mountain Lion for me. Indeed, switching my late 2011 Macbook Pro to dedicated graphics solves the problem. But, I prefer to stick to integrated graphics to save battery life. A web browser shouldn't require dedicated graphics to run reliably. Quitting Safari and restarting it also temporarily solves the problem, but it comes back fairly quickly. The problem even persists after a full reformat (which I did for unrelated reasons). So, I've had enough.

I've switched to Firefox until this is resolved. These glitches aside, I've been happily using Safari exclusively since Safari 5. Until Mountain Lion was released, it ran perfectly on my Macbook Pro and on my old 2008 Macbook. The iCloud integrated features are wonderful. I love having my bookmarks synced to my iPhone. The tab syncing has been exceptionally useful. But, I'm going to have to do without those features for a while. I'll give Safari another try once the next version is released.

So, Apple, please fix this. Safari is a great browser, and were it not for these glitches, I'd still be using it.

PS: You have no idea how nice it feels to type some text in a browser without it glitching and messing up with every character I type.