Rendering(?) problem when browsing, Chrome's fault?

Discussion in 'MacBook Pro' started by nassosdim, Jan 27, 2012.

  1. nassosdim, Jan 27, 2012
    Last edited: Jan 29, 2012

    nassosdim macrumors newbie

    Joined:
    Aug 12, 2011
    #1
    Hello everyone,

    I have a MacBook Pro 13'', mid-2010 model and recently I began noticing something annoying. It seems that when I'm browsing with Chrome and I scroll a web page there's a chance that the page will start looking like this:

    http://cl.ly/1L023v1W2K0O393n231R

    I honestly don't know who to blame: Some people refer to this as a graphics card problem while others as a Chrome one.

    Please help. :(

    Edit: Stop the press, we've got an update!

    http://www.google.com/support/forum/p/Chrome/thread?tid=0a971e592359a34a&hl=en

    A person who has the same problem reports that it happened when he was using Xcode. So it's not a Chrome-exclusive issue.
     
  2. malman89 macrumors 68000

    Joined:
    May 29, 2011
    Location:
    Michigan
    #2
    Pretty sure it's a Chrome problem... perhaps in collaboration with your GPU. I get the same issue - though not that bad and very rarely - when using Chrome in Windows XP or OSX. It happens when Alt+Tabbing or Command+Tabbing from something - say the desktop - to Chrome, right? Or another program to Chrome. Then there's that distorted mixing of whatever is behind it or just switched from.
     
  3. thundersteele macrumors 68030

    Joined:
    Oct 19, 2011
    Location:
    Switzerland
    #3
    There is a known problem with the 2010 GPUs, but I'm not sure if this is the same issue. Maybe some of the suggestions in the link below are helpful.

    http://support.apple.com/kb/TS4088
     
  4. Andy156 macrumors newbie

    Joined:
    Mar 21, 2011
    #4
    Thank god. I thought it was just my GPU. I only have this problem when I try using Chrome.
     
  5. nassosdim, Jan 28, 2012
    Last edited: Jan 28, 2012

    nassosdim thread starter macrumors newbie

    Joined:
    Aug 12, 2011
    #5
    No, that's not it. Mine's the 13-inch model.

    Edit: Stop the press, we've got an update!

    http://www.google.com/support/forum/p/Chrome/thread?tid=0a971e592359a34a&hl=en

    A person who has the same problem reports that it happened when he was using Xcode. So it's not a Chrome-exclusive issue.

    Gonna downgrade to Snow Leopard later today if this won't be resolved.
     
  6. thundersteele macrumors 68030

    Joined:
    Oct 19, 2011
    Location:
    Switzerland
    #6
    Ok, I see. Have you considered bringing the laptop to Apple for an inspection?
     
  7. brianfast macrumors regular

    Joined:
    Jun 11, 2010
    #7
    This is known problem, but Apple is ignoring it. I also use Chrome, but I have also seen the error in Safari

    http://forums.macrumors.com/showthread.php?t=1196552&page=2
    http://att.macrumors.com/showthread.php?t=1307621
     
  8. nassosdim thread starter macrumors newbie

    Joined:
    Aug 12, 2011
    #8
    After downgrading to SL I used Chrome for hours, scrolling through blogs and wallpaper collections. So far no issues. I haven't installed Xcode yet but I'll do it tomorrow. From the looks of it it's clearly GPU drivers under Lion that frak up the rendering with artifacts.

    Totally unacceptable.
     
  9. alphaod macrumors Core

    alphaod

    Joined:
    Feb 9, 2008
    Location:
    NYC
    #9
    So instead of using another perfectly functional browser (ie: Firefox, Safari, Opera), you decided it was easier to reinstall the OS? :confused:
     
  10. nassosdim, Jan 29, 2012
    Last edited: Jan 29, 2012

    nassosdim thread starter macrumors newbie

    Joined:
    Aug 12, 2011
    #10
    Which part of the "happens in Xcode too" did you missed?

    Now, let's get something straight:

    a) People with other MBP's use Xcode and Chrome without this issue (means it's not application's fault).
    b) This issue doesn't happen in my MBP under Snow Leopard (means it's not my faulty hardware).
    c) Other people also get this http://forums.macrumors.com/showthread.php?p=14235556#post14235556

    Not Chrome's fault.
     

Share This Page