netkas.org

MBP2012/10.7.5 nvidia drivers are leaky

The nvidia drivers from mbp2012(and from 10.7.5 beta, they are same) are really leaky one.

For example, yeasterday I had a site with many flash ads openned in opera and bam, kernel (kernel_task, video driver is part of it) eats 690 MB of memory. Normally its around 200mb.

Watching an online video in flash player – 700 mb for kernel_task

Only happens when nvidia card installed, no problem with ati.

Be aware.

Comments

  1. July 2nd, 2012 | 10:35 am

    10.8(12A256) kernel_task — 678MB 🙁

  2. corehoundboi
    July 2nd, 2012 | 12:39 pm

    Flash is dead any way use HTML5 … any thing that doesnt upgrade to HTML5 Players is prob trashy or porn any way. Join a p Tracker lol

    Heaps of Crashes on Win8 CP with flash atm tooo its being left to die adobe discontinue it completely in afue years. Its also the number1 way to get hacked and kill your battery life dont install dat shit unless your single

  3. Petr
    July 2nd, 2012 | 12:56 pm

    Thats is interesting – I was not aware that kernel_task was supposed to be that small! Mine is around 1.2GB pretty much all the time, using ATI 6870.

    And the only non-apple kexts are following:
    com.rogueamoeba.InstantOn (5.0.1)
    org.netkas.FakeSMC (3.1.0)
    com.lnx2mac.driver.RealtekRTL81xx (0.0.67)
    at.obdev.nke.LittleSnitch (2.4.4)
    com.Logitech.Control Center.HID Driver (3.5.1)
    com.Cycling74.driver.Soundflower (1.5.3)
    com.vmware.kext.vmx86 (0049.15.87)
    com.vmware.kext.vmci (90.1.1)
    com.vmware.kext.vsockets (90.1.3)
    com.vmware.kext.vmioplug (0049.15.87)
    com.vmware.kext.vmnet (0049.15.87)

    So.. how can I tell which kext is using which portion of the memory?

  4. macwanabe
    July 2nd, 2012 | 2:36 pm

    Mountain Lion Latest my kernel_task is using 1.88GB “Real Mem” using Nvidia GTX 570

  5. Yolanda
    July 2nd, 2012 | 7:34 pm

    And what with drivers from latest 10.8 build?

  6. iLeopod
    July 2nd, 2012 | 9:09 pm

    The problem might be that VideoHardwareAcceleration is not enabled withe the most nvidia cards. We all taking often about opencl but i bet more user would profit from VDADecode. Would really appreciate if someone find bin patch or a other method to get it working. I already tryed some suff but failed.

  7. July 2nd, 2012 | 11:33 pm

    […] d’un MacBook Pro 2011 tous deux dotés de 16 Go de RAM et dans des usages identiques.Netkas a mis le doigt sur ce qui consomme tant de […]

  8. Stefe Hobs
    July 3rd, 2012 | 12:37 am

    VDADecode would be really fine. i also have tested a lot of things, but i think we need a bin-patch to make it work of.

  9. netkas
    July 3rd, 2012 | 8:02 pm

    >Mountain Lion Latest my kernel_task is using 1.88GB “Real Mem” using Nvidia GTX 570

    My work’s Imac with ati 4670 – kernel_task 350 mb after 2 days of uptime and very intensive use (xcode, adobe flash, idea)

    so 700 mb or 1.88gb is NOT NORMAL

  10. Stefe Hobs
    July 3rd, 2012 | 9:21 pm

    32bit kernel = round about 240mb (geforce 9800gt)
    64bit kernel = round about 480mb (geforce 9800gt)

    32bit kernel = round about 240mb (radeon hd 4670)
    64bit kernel = round about 285mb (radeon hd 4670)

    all values ​​after a few hours of using lion 10.7.4

  11. npwski
    July 4th, 2012 | 11:39 am

    At 10.7.5
    bash-3.2# kextstat | grep -i hal
    46 0 0xffffff7f812cf000 0x329000 0x329000 com.apple.nvidia.nvGF100hal (7.2.8)
    77 0 0xffffff7f80fcc000 0x303000 0x303000 com.apple.nvidia.nvGK100hal (7.2.8)
    78 0 0xffffff7f80ca9000 0x323000 0x323000 com.apple.nvidia.nv50hal (7.2.8)

    Maybe it’s too much nvidia kexts loaded? Maybe nvGF100hal it’s enough for my fermi GTX580 )

    /// loaded doesnt mean attached&handling device.
    ///if its loaded and not attached, like gk100 kext here, it jsut hanging in memory doing nothing

  12. Switched
    July 6th, 2012 | 2:28 pm

    Will Mountain Lion support unflashed PC GPUs in real Macs?

    I have seen claims that some has used a 6870 unflashed in a Mac Pro in Lion, is this possible?

    Great site netkas

  13. July 8th, 2012 | 6:50 pm

    I dont’ know netkas, were you having some home made vodka when you looked at those numbers? (you know it should be made with ethanol not methanol, right?) 🙂

    200MB for a kernel_task is incredible for Lion, maybe in Snow Leopard could be.

    I’ve booted Lion .4 on a macpro3,1 and my kernel task is 690MB, 48 min uptime. This system has HD 3870 in it so it’s not like it has some latest and the greatest video card…

  14. nspyro
    July 8th, 2012 | 11:18 pm

    After reading this I checked my kernal_task, and it was using 1.90GB real mem. MacPro 4,1 (5,1 firmware) GTX570

  15. Czarek
    July 10th, 2012 | 12:03 pm

    On my Mac Pro 5.1 with official ATI 5770 without any hacky kexts kernel_task is 692 MB so I think this is normal.

  16. July 15th, 2012 | 7:19 am

    Same issue in 10.8 GM

  17. Sergee
    July 30th, 2012 | 7:05 am

    Also, strange bricky color artifacts in picture appears when resume from sleep in 10.8 with my gt440. In 10.7.4 all worked perfectly w/o any problem. In 10.8 i have too many chances to reset because i lose desktop view, it hidden behind artifacts

  18. joe
    August 1st, 2012 | 5:07 am

    With both 10.7.x and 10.8 I have the same behaviour. mid-2010 (6,2) MBP 15″. After a fresh reboot, kernel_task consumes around 400MB – some hour later its up to 520MB. 3 days later i’m sitting around 850-900MB…and so it goes on until I reboot.

    This has to be a known issue.

Leave a reply