Apple Event: May 7th at 7 am PT

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Safari 10.0.2 (11602.3.12.0.1) Memory Leak?

I just installed the latest version of Safari onto my MacBook running 10.11.6. Safari has crashed several times and at one point it was using 75GB of memory according to Activity Monitor, it is currently at 24GB, with a single tab open.


Even just sitting watching the memory utilization it constantly climbs, with nothing happening in the browser.


Has anyone else experienced this?

MacBook Pro (Retina, 15-inch, Late 2013), OS X El Capitan (10.11.6)

Posted on Dec 14, 2016 1:19 PM

Reply
52 replies

Dec 14, 2016 1:55 PM in response to stedman1

I can't post the data from EtreCheck, this community keeps complaining that there are invalid characters.


Top Processes by CPU:

55% Safari

4% WindowServer

2% kernel_task

1% fontd

1% WebEx Productivity Tools


Top Processes by Memory:

3.04 GB Safari

1.25 GB kernel_task

623 MB com.apple.WebKit.WebContent(2)

246 MB WacomTabletDriver

180 MB Dock

Dec 14, 2016 9:08 PM in response to Stephen Donovan

Hello Stephen,

Could you e-mail your report to Etresoft support? In EtreCheck, go to Help > Etresoft support.


I think I know what the problem is. Someone else reported something similar. You probably have some software version that contains the magic characters that trigger the Apple Support Communities spam filter. It is a special sequence of numbers that forms part of the phone number for an Indian astrology spammer.

Dec 15, 2016 8:39 PM in response to Stephen Donovan

I'm on the new 15 inch "touch pad" MacBook Pro, just updated to 10.12.2 last night so uptime was only 16 hours at the time. I had a few tabs open on Safari and everything just died (as you can see). I killed each paused process and everything is now working fine. That said Safari is now using 50GB and climbing.


Something is definitely leaking here...

User uploaded file


-John Davies-

@jtdavies

Dec 16, 2016 7:43 AM in response to Stephen Donovan

Safari/Preferences/Advanced - enable the Develop menu, then go there and Empty Caches. Quit/reopen Safari and test. Then try Safari/History/Show History and delete all history items. Quit/reopen Safari and test. You can also try try Safari/Clear History…. The down side is it clears all cookies. Doing this may cause some sites to no longer recognize your computer as one that has visited the web site. Go to Finder and select your user/home folder. With that Finder window as the front window, either select Finder/View/Show View options or go command - J. When the View options opens, check ’Show Library Folder’. That should make your user library folder visible in your user/home folder. Select Library/Caches/com.apple.Safari/Cache.db and move it to the trash.


Go to Safari Preferences/Extensions and turn all extensions off. Test. If okay, turn the extensions on one by one until you figure out what extension is causing the problem.


Safari Corruption See post by Linc Davis




Dec 16, 2016 11:41 AM in response to Eric Root

I Emptied the Cache and restarted, Safari memory usage was still climbing.

I only have a single extension active, which is AdBlock, disabling that didn't appear to have any improvement.


I noticed that there are others complaining about issues in Safari. One of the other complaints was some history not being available, which is consistent with my problem.

Dec 17, 2016 6:22 AM in response to Stephen Donovan

Very much the same report as my earlier post but a little more information. It takes roughly 18 hours for my Safari to get to 50GB of memory usage. It climbs whether I use it or not but apparently faster when you use it. I've had just one tab open and no difference, I have no plugins or extensions. My (touch bar) 15 inch MBP is brand new and I've installed all the software from scratch. Safari uses a single core 100% all the time from reboot to crash although when I put up the "about" to get the screen shot below it hit 200% after a few seconds and then crashed. The only recourse is to kill the process and restart Safari. Naturally when you do it uses 100% of a core again. In the 10 minutes it's taken me to write this since the restart Safari is now using 2.7GB and climbing.


First shot after it's crashed, Safari has been running about 18 hours.


User uploaded file


Second shot a few seconds after Safari restart, note memory pressure, swap and CPU usage.


User uploaded file


And as I type this message...

User uploaded file

Safari 10.0.2 (11602.3.12.0.1) Memory Leak?

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