{"id":508,"date":"2006-04-09T01:21:22","date_gmt":"2006-04-09T09:21:22","guid":{"rendered":"http:\/\/www.wiredatom.com\/blog\/2006\/04\/09\/safari-still-unbearable\/"},"modified":"2006-04-09T01:26:44","modified_gmt":"2006-04-09T09:26:44","slug":"safari-still-unbearable","status":"publish","type":"post","link":"https:\/\/www.wiredatom.com\/blog\/2006\/04\/09\/safari-still-unbearable\/","title":{"rendered":"Safari Still Unbearable"},"content":{"rendered":"<p>After ditching Firefox for Safari less than 48 hours ago, I am back using Firefox again. Safari&#8217;s memory leak was simply unbearable. After doing some surfing on how to boost both Safari and Firefox&#8217;s performance as well as reduce potential for memory leaks, I came across this nifty command line to check leaks:<\/p>\n<blockquote><p>\nFor Safari, in the command prompt, run<\/p>\n<div class=\"codecolorer-container text railscasts\" style=\"overflow:auto;white-space:nowrap;width:680px;\"><table cellspacing=\"0\" cellpadding=\"0\"><tbody><tr><td class=\"line-numbers\"><div>1<br \/>2<br \/>3<br \/>4<br \/>5<br \/>6<br \/>7<br \/><\/div><\/td><td><div class=\"text codecolorer\">cosmo:~ zzz$ leaks Safari<br \/>\nProcess 16320: 296847 nodes malloced for 47252 KB<br \/>\nProcess 16320: 56 leaks for 6176 total leaked bytes.<br \/>\n.<br \/>\n.<br \/>\n.<br \/>\n(lines and lines or error codes)<\/div><\/td><\/tr><\/tbody><\/table><\/div>\n<p>For Firefox, run<\/p>\n<div class=\"codecolorer-container text railscasts\" style=\"overflow:auto;white-space:nowrap;width:680px;\"><table cellspacing=\"0\" cellpadding=\"0\"><tbody><tr><td class=\"line-numbers\"><div>1<br \/>2<br \/>3<br \/>4<br \/>5<br \/>6<br \/>7<br \/><\/div><\/td><td><div class=\"text codecolorer\">cosmo:~ zzz$ leaks firefox-bin<br \/>\nProcess 16320: 309998 nodes malloced for 47750 KB<br \/>\nProcess 16320: 111 leaks for 3440 total leaked bytes.<br \/>\n.<br \/>\n.<br \/>\n.<br \/>\n(lines and lines of error codes)<\/div><\/td><\/tr><\/tbody><\/table><\/div>\n<\/blockquote>\n<p>When<\/p>\n<div class=\"codecolorer-container text railscasts\" style=\"overflow:auto;white-space:nowrap;width:680px;\"><table cellspacing=\"0\" cellpadding=\"0\"><tbody><tr><td class=\"line-numbers\"><div>1<br \/><\/div><\/td><td><div class=\"text codecolorer\">leaks Safari<\/div><\/td><\/tr><\/tbody><\/table><\/div>\n<p>was executed, the error codes ran for pages and pages in the command prompt. It was so long that the command prompt&#8217;s buffer ran out of memory (and only after I piped the errors to a text file did I find out that the error code generated a 20MB plain text file!!). And that was after I launched Safari fresh with 10 tabs. In comparison, Firefox&#8217;s error code was only a few mouse scrolls away. On top of that, after only having used Safari for less than 12 hours yesterday, I watched it gobbling up almost 200MB of RAM where as in Firefox, I can go on for days with keep the memory occupancy at less than 135MB. Again, this was all with about 10 tabs opened simultanously at all times.<\/p>\n<p>After I decided to quit Safari (<i>again<\/i>), I closed the windows one by one after transfering all the pages to Firefox. And it gave me this error:<\/p>\n<blockquote><p>\nThe following world leaks were detected (the check is done when all browser windows are closed):<\/p>\n<p>2 WebView objects, 1 WebFrame object, 1 WebDataSource object, 1 WebFrameView object, 1 WebHTMLRepresentation object, 1 WebBridge object, 2 JavaScript interpreters.<\/p>\n<p>Please write a bug report about this, along with reproducible steps if possible.\n<\/p><\/blockquote>\n<p><img loading=\"lazy\" decoding=\"async\" src=\"\/images\/safari_leaks.png\" width=\"400\" height=\"243\" class=\"centered\" alt=\"Safari Leaks\" \/><\/p>\n<p>Supposedly Finder and almost everything else leaks memory as well&#8230; But I am surprised the OS holds up so well after having gone weeks (sometimes months) without a reboot&#8230; I wonder how XP and\/or other OSes and their Desktops\/X hold up against leaks. But I have never heard of Linux having to restart from crashes or bad memory leaks. And OSX has been pretty stable for the past 3.5 years in various versions I have been using. So Windows must just suck more then? <\/p>\n<p>Argh&#8230; memory leaks are annoying&#8230;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>After ditching Firefox for Safari less than 48 hours ago, I am back using Firefox again. Safari&#8217;s memory leak was simply unbearable. After doing some surfing on how to boost both Safari and Firefox&#8217;s performance as well as reduce potential for memory leaks, I came across this nifty command line to check leaks: For Safari, &hellip; <a href=\"https:\/\/www.wiredatom.com\/blog\/2006\/04\/09\/safari-still-unbearable\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Safari Still Unbearable&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2}},"categories":[10,3,6],"tags":[],"class_list":["post-508","post","type-post","status-publish","format-standard","hentry","category-geek-stuff","category-mac-osx","category-rant"],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p54IqZ-8c","_links":{"self":[{"href":"https:\/\/www.wiredatom.com\/blog\/wp-json\/wp\/v2\/posts\/508","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.wiredatom.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.wiredatom.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.wiredatom.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.wiredatom.com\/blog\/wp-json\/wp\/v2\/comments?post=508"}],"version-history":[{"count":0,"href":"https:\/\/www.wiredatom.com\/blog\/wp-json\/wp\/v2\/posts\/508\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.wiredatom.com\/blog\/wp-json\/wp\/v2\/media?parent=508"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.wiredatom.com\/blog\/wp-json\/wp\/v2\/categories?post=508"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.wiredatom.com\/blog\/wp-json\/wp\/v2\/tags?post=508"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}