I use the latest "WebKit-604.4.5-Leopard-PowerPC.dmg" on a G4 Cube (!), running OS X 10.5.8.
Webkit works fine when initialy started.
But very quickly it saturates the available memory (1.5GB) and when it reaches this limit, Webkit crawls down to a snail.
Closing Webkit windows and tabs does not help.
Only restarting Webkit helps... for a few minutes, until the problem starts again.
The problem seem to be much worse with multiple tabs, and minimized when only a single window / single tab is used.
Let me know what kind of additional information I can provide to help solve this annoying ssue.
Would be absolutely great if you could provide steps for reproducing it that quickly!
I've seen this happen quite frequently but I don't know how to reproduce it - the browser uses to run rather well for quite some days. But if you could tell me a trick to quickly force this I'hopefully be able to finally find and fix the issue!
Please tell me what sites you're visiting and whether you are using Safari extensions like ad blockers or Safari hacks like Glims (which I've been using for several years).
I know that complex flash content will very reliably shoot down your browser within a short time. And ad blocker extensions are very resource hungry, too - and lighter and faster alternatives are available.
Futhermore you could test whether Roccat (relinked to Leopard WebKit) exposes the same issue for you.
Last edit: Tobias Netzel 2017-11-22
Hi Tobias, here is the way to reproduce it quickly :
Threads : 15
Real Memory : 87.25MB
Virtual Memory : 357.20MB
Threads : 75
Real Memory : 1.20GB
Virtual Memory : 1.66GB
When this stage is reached, closing the Tabs does not help, opening new Tabs only makes it worse, and WebKit crawls down (and everything else too); you have to restart WebKit to free the memory.
Just in case, here are the URLs of the 7 tabs :
https://www.ebay.fr/sch/i.html?_from=R40&_sacat=0&_nkw=LED+COB+B22&rt=nc&_dmd=2
https://www.ebay.fr/sch/i.html?_from=R40&_sacat=0&_nkw=LED+COB+B22&rt=nc&_dmd=2
https://www.ebay.fr/itm/Vintage-B22-E27-LED-COB-4W-G95-ST58-A60-Globe-Cage-Ampoule-Edison-Filament-Lampe/132204166539?hash=item1ec7fb7d8b:m:mwoo7Qkf6oH-da5YSmNNGpQ
https://www.ebay.fr/itm/E27-E14-B22-GU10-G9-4014SMD-LED-Corn-Bulb-12W-18W-25W-30W-35W-Clair-Lampe-220V/272722136920?hash=item3f7f818f58:m:m4TyQd5FqbRC4DOFQ4DWDUA
https://www.ebay.fr/itm/8x-Filament-E14-3W-6W-8W-AC-220V-ampoule-LED-COB-Bougie-Flamme-Lumiere-Lampe/162755843110?hash=item25e5011426:m:mvpZtMdSc5t-3-ekn3oKYyg
https://www.ebay.fr/itm/E14-E27-B22-GU10-G9-LED-Corn-Bulb-4014SMD-12-18-25-30-35W-Clair-220-240V-Lampe/301994934644?hash=item46504d0174:m:m4TyQd5FqbRC4DOFQ4DWDUA
http://www.ebay.fr/itm/GU10-E14-E27-G9-B22-36-56-72-96-138-LED-4014-SMD-Housse-Mais-Ampoule-Lamp-Phare/302423728665?hash=item4669dbe219:m:mY1y9sZSwWtFakj58AcdEjw
Here are my Plug-Ins and Extensions :
Safari 5.06 (5533.22.3, 5604) / Webkit r223797
Extensions [user / Library / Safari / Extensions] :
SafariRestore 7.1.7
Adblock Plus 1.12.4
ClickToFlash 3.2
ClickToPlugin 3.2
Ghostery 5.4.10
DuckDuckGo 1.8.0
Module complémentaire de navigateur pour la désactivation de Google Analytics
Plus-ins [boot_disk / Library / Internet Plug-Ins] :
AdobePDFViewer.plugin” 9.5.5
Flip4Mac WMV Plugin.plugin 2.4.4.2
Quartz Composer.webplugin 1.1
QuickTime Plugin.plugin 7.7
RealPlayer Plugin.plugin
Flash Player.plugin 11.1 r102
JavaPluginCocoa.bundle 12.9.0
VerifiedDownloadPlugin.plugin 1.0
I will check for the relinked Roccat and let you know the results.
Thanks for your help.
I just checked, and "Roccat LepWK.app" [relinked with WebKit-604.4.5-Leopard-PowerPC.dmg] has the same problem : memory is not freed when you close Tabs, and you have to restart the browser to free it.
Roccat.app [NOT-LepWK] has a much slower memory growth.
Just for providing some background information: WebKit doesn't immediately free memory when closing tabs or windows because it keeps the "pages" in its page cache. A certain number of pages are always kept in that cache; if I remember correctly Roccat sets a smaller page cache size than Safari.
So the observed behaviour is to be expected - to some extent.
I just gave it a try by doing that search on ebay in the Safari session that I've been using since yesterday.
I used the command line developer tool 'vmmaps' for examining Safari's memory usage.
Before opening those ebay pages the following summarized values were determined:
After opening and fully loading those pages the values were like this:
And after closing all the newly opened tabs:
So while the memory usage increased for opening the ebay pages, it was even lower than initially after closing again all of them.
So appearantly all caching mechanisms work like they should - I wouldn't have expected these quite good results. But there ARE some cases where memory usage rapdly increases without decreasing later on. I'll further investigate...
Do you get the same results with extensions disabled?
Instead of Adblock Plus I'd recommend Privoxy - although it might not be as easy to use as Adblock Plus.
Instead of SafariRestore I'd recommend using Glims for Safari.
In my experience ClickToFlash/ClickToPlugin aren't that useful any longer. Since quite some months I'm browing without them - and they shouldn't be used on youtube any longer since they force loading the flash versions of the videos in order to being able to replace them.
See [Home] (at the bottom) for recommended extensions and add-ons.
Related
Wiki: Home
I uninstalled and disabled ALL extensions; I kept all previous plug-ins active.
The memory growth is quite slower, and I need to open about 12-15 ebay Tabs to reach the same memory usage as before.
BUT when I close all those Tabs, the memory is again NOT released, neither the "Active" nor "Inactive/Cached" part.
I tried to close the last Tab/Window, but then Webkit hanged on, and I had to force quit.
Would it help if I could install your 'vmmaps' tool ? But if it just gives the pages total and does not trace what procedure uploads what, then I suspect it won't help much...
I am sorry my "quick way for reproducing the problem" is not so reproduceable on your side.
I know memory leaks are quite a pain to eradicate, especially when it is not even obvious if it is a 10.5.8, Safari 5.0.6 or WebKit issue. At least we know it is not an Extension issue, although Extensions make it worse, and it does not seem to be a Safari 5.0.6 issue since Roccat LepWK has the same problem.
'vmmap' provides a lot of information - those lines are the most summarized output from it.
It is actually possible to log all memory allocations by sourcecode line - but it needs some GB of free RAM for not taking the whole night (constantly swapping memory between the hard drive and RAM). So using those tools would only be possible on a PowerMac G5 - which I don't own.
For the sake of completeness, I also disabled ALL Plug-Ins in addition to disabling ALL Extensions.
No difference : the WebKit Active and Inactive memory is not released unless I quit WebKit