Existing users, log in.  New users, create a free account.  Lost password?


MacFixIt Logo
 
Contact Us | About MacFixIt | Who's Online  

You are not logged in. MacFixIt Forums » Forums » Networking & Cross-Platform » Internet Related » Safari 4.0 & Memory Leak
Register User    Forum List        Active Topics     Search     FAQ
Page 2 of 2 < 1 2
Topic Options
#471870 - 06/10/09 09:58 AM Re: Safari 4.0 & Memory Leak [Re: macnerd10]
tacit Offline
MacGuru

Registered: 10/14/99
Posts: 12002
Loc: Portland, Oregon, USA
Originally Posted By: macnerd10
Mine is like this (2.3 GHz DP PPC G5, 1 GB RAM, OS 10.5.7):
Threads: 9
Real memory: 24 MB
Virtual memory: 810 MB
This is on a standstill (no surfing).
This looks similar to Pendragon's relaunch status.
P.S. On a positive note, version 4.0 loads pages even faster than iCab.


Wow, your usage is radically different from mine. At the moment, with my computer recently restarted, I'm looking at:

Safari
Threads: 8
Real memory: 246.50 MB
Virtual memory: 2.35 GB
_________________________
---
Photo gallery, all about me, and more: www.xeromag.com/franklin.html
RIP MacFixIt! New Mac forum: finetunedmac

Top
#472025 - 06/11/09 02:04 PM Re: Safari 4.0 & Memory Leak [Re: Alam Khan]
macnerd10 Offline
MacAuthor

Registered: 12/27/01
Posts: 2217
Loc: Los Angeles, CA, USA
Back to memory leak: if I have several browsers open, Safari uses up less memory on a standstill, both real and virtual than others (iCab, Firefox, Opera):
Firefox (real/virtual, MB): 50/856
Safari 24/810
Opera 38/841
iCab 129/1100 (I am typing in it now)
For comparison, Adobe Reader 9 is as follows: 86/923.
_________________________
Alex
2.66 GHz 17" MacBook Pro, 4 GB RAM, OS 10.5.7, Office 2008, TimeWarner Cable

Top
#472155 - 06/12/09 11:00 PM Re: Safari 4.0 & Memory Leak [Re: macnerd10]
cyn Offline
MFIF Admin

Registered: 03/20/01
Posts: 5226

I moved a branch of replies from this thread over to a separate topic: Safari 4 "Request-URI Too Large"
_________________________
MacFixIt Forums Admin

Top
#473455 - 06/27/09 10:14 AM Re: Safari 4.0 & Memory Leak [Re: pendragon]
Hal Itosis Offline
MacWizard

Registered: 08/23/99
Posts: 7032
Loc: 10.5.7 (build 9J61)
Originally Posted By: pendragon
The (serious?) memory leak continues in Safari 4.0, at least for me.

After quitting Safari and relaunching, I can open Activity Monitor and watch the both the Real Memory and Virtual Memory rise. Of course, the more pages I surf/the longer Safari is open, the greater the leak. Fortunately, I see no adverse effects from this leak (yet).

I found no solution other than quitting and then restarting Safari.

Bad conclusions on my part, or is there a memory leak fix?

If any thread is going to confirm (or refute) Safari's leakiness, this one should: Giant Safari memory leak

--

Thus far, indications are it may have more to do with "add-ons" than Safari itself.


Edited by Hal Itosis (06/27/09 01:06 PM)
Top
#473508 - 06/28/09 05:38 AM Re: Safari 4.0 & Memory Leak [Re: Hal Itosis]
pendragon Offline
MacAuthor

Registered: 11/14/99
Posts: 1565
Loc: Georgetown, TX, USA
Maybe relief/a solution (sorta) is on the way-

See 9 to 5 Mac, quoted in part below:

"New in Snow Leopard: Activity Monitor shows you exactly what is killing your CPU.

Before, you'd just see that Safari was nailing your CPU. Now there's a more specific breakdown, which shows the true culprit. Plug-in sandboxing is good thing. It is especially helpful when a plug-in is not responding and you want to quit it without killing your browser session (below)."

I hope this post doesn't muddy the waters...
_________________________
Harv
24" Intel (Core 2 Duo) iMac, 10.5.7

Those who can make you believe absurdities can make you commit atrocities. ~Voltaire

Top
#473540 - 06/28/09 12:09 PM Re: Safari 4.0 & Memory Leak [Re: pendragon]
Hal Itosis Offline
MacWizard

Registered: 08/23/99
Posts: 7032
Loc: 10.5.7 (build 9J61)
Originally Posted By: pendragon
Maybe relief/a solution (sorta) is on the way-

See 9 to 5 Mac, quoted in part below:

"New in Snow Leopard: Activity Monitor shows you exactly what is killing your CPU.

Before, you'd just see that Safari was nailing your CPU. Now there's a more specific breakdown, which shows the true culprit. Plug-in sandboxing is good thing. It is especially helpful when a plug-in is not responding and you want to quit it without killing your browser session (below)."

I hope this post doesn't muddy the waters...

Well, CPU hogging and memory leaking aren't necessarily due to the same culprit... but it could be possible sometimes. Usually Flash and/or Javascripts on a page can cause Safari (or any browser) to go wild, when they're written inconsiderately. I wonder if that Activity Monitor feature would reveal that detail.

Top
Page 2 of 2 < 1 2


Moderator:  alternaut, dianne, dkmarsh 

VersionTracker: Software Updates and Downloads | iPhone Atlas: iPhone Help, News, Tutorials, and Tips