rMBP 15 running hot with Chrome because of it use GT650m?

Discussion in 'MacBook Pro' started by darkinners, Mar 19, 2013.

  1. darkinners macrumors member

    Joined:
    Mar 15, 2013
    #1
    Today I found whenever I use Chrome.
    My rMBP has A LOT of temperature spike, usually last for 10-15 seconds (65-75 degrees Celsius) ambient around 25 degree Celsius.


    Then I found Chrome uses GT650m instead of HD4000 in iStatmenus.

    Could this be the culprit? If yes. Any way I solve this?





    I tried Safari 6.0.3 and latest webkit.

    Both doing the same stuffs as Chrome did. Same website, same tabs.
    The temp never excess 55 degree Celsius.

    And I also notice whatever I browser on Safari. It only use HD4000, instead of triggering GT650m like Chrome did.



    Also in iStatmenus, I found both Chrome and Webkit utilize multicore.
    But I noticed Chrome use WAY more resource to do same thing Webkit does and in Chrome the UI performance even much less smooth than Webkit.

    I think this contribute to the temp spike as well.



    I tested both with charger plugged in and battery only.
    Same result.
    Also made sure "automatic graphics switching" checked in Energy Saver


    I know I can always uninstall Chrome and use Webkit.
    But few things made me not doing so.
    1. Extensions - I have some work related extensions have no replace in Safari or at least not as efficient

    2. Chrome sync everything with my PC, Mobile phone which is very convenient for me.



    So If possible, I want to stick with Chrome. annoyed by the UI performance but not annoyed enough to ditch Chrome.

    However the temp does. I use my laptop on my laptop quite often. heat would be a really big concern to me. Summer is coming here.


    Sorry for the wall of text and poor grammar(English is not my native tongue)
    Thanks in advance to anyone that can help or contribute.:)
     
  2. GGJstudios macrumors Westmere

    GGJstudios

    Joined:
    May 16, 2008
    #2
    Those temps are quite normal, and not a cause for concern. If you're not already doing so, use iStat Pro (free) or iStat Menus ($16) to get accurate readings of your temps, fan speeds, etc., rather than relying on your sense of touch or sound. A forum member has posted a copy of iStat Pro that has been "tweaked" to enhance compatibility with Mountain Lion. You can download it here.

    The Intel processors used in Macs are designed to automatically shut down to prevent damage if they truly overheat. CPU Tjmax = 105C (221F), GPU Tjmax = 100C (212F) on i3, i5, i7 processors. (Source: Intel)

    Unless there is a rare defect in a Mac, most temps are well within the normal operating range, considering the workload being put on it. Websites with Flash content, games and other multimedia apps will put higher demand on the CPU/GPU, generating more heat. This is normal. If you're constantly putting high demands on your system, such as gaming or other multimedia tasks, expect temps to rise and fans to spin up accordingly. It's just your Mac doing its job to maintain temps within the normal range.

    It is also quite normal for your Mac to become extremely hot to the touch during intensive operations. The aluminum body transfers heat more effectively than other materials used in computer casings, so you will feel the heat more. This doesn't indicate that it's overheating and will not harm the computer to be hot to the touch.

    Your fans are always on when your Mac is on, spinning at a minimum of 2000 rpm (for MBPs) or 1800 rpm (for MBAs, MBs and minis). iMacs have 3 fans with minimum speeds in the 800-1200 range. They will spin faster as needed to keep temps at a safe level.

    If your fans are spinning up without increased heat, try resetting the SMC.
    (PRAM/NVRAM has nothing to do with these issues, so resetting it will not help.)

    The intake and exhaust vents are in the back of the computer near the hinge on all Mac notebooks (except the new MBP with retina display, which has intake vents along the sides at the bottom). The iMac vent is a slot on the back near the top of the computer. Make sure the vents remain unblocked to allow your computer to perform at its best.

    Learn about the fans in your Mac
    Apple Portables: Operating temperature

    For Flash-related issues:
     
  3. locoboi187 macrumors 6502a

    Joined:
    Oct 3, 2012
    #3
    Safari > Bookmarks > Show all bookmarks

    You should see chrome on the left. Thats how I got my bookmarks over a while ago
     
  4. darkinners thread starter macrumors member

    Joined:
    Mar 15, 2013
    #4
    Thank you you both!

    I think I found out the rapt cause.

    IT caused by I disabled Chrome's built in Flash because Chrome built in flash are very laggy in youtube fullscreen playing and every time I switch to fullscreen it will have 1-2 second white screen problem.

    So I disabled the Chrome built in flash and use the system Flash instead
    (actually both are the same version)

    I go back and enable the Chrome built in flash. GT650m trigger problem gone.
    Very good temp, in trade of almost unplayable youtube fullscreen video.



    By the way locoboi187, care to elaborate please? about the Chrome bookmarks in Safari


    I did what you told me.

    Bookmarks->show all bookmarks


    There is no "Chrome" or anything reassemble of Chrone bookmarks on the left panel.
    Did you do it wrong? Or I need to get some Safari extension/enable something to get to enable Safari to sync Chrome's bookmarks? Thanks!
     
  5. dusk007 macrumors 68040

    dusk007

    Joined:
    Dec 5, 2009
    #5
    You can use gfxCardStatus to force the HD 4000 all the time.
    Apple's auto switching is dumb and only Apple's own Safari manages to prevent it from going nuts. The switching is broken. I often force the IGP all the time in OSX. I use the dedicated only ever for gaming, Windows or external screens. Browsing and Office OSX work doesn't need any 650M ever but sometimes a little java program can trigger a dedicated GPU and once switched it won't switch back even if the evil program causing it only used the wrong framework for a split second once and runs for days in the background doing nothing.
     

Share This Page