![]() ![]() Memory is NOT reclaimed if the user navigates elsewhere. In Firefox and Safari, and very possibly other browsers, if there's no window.onunload handler then memory is only reclaimed when the window is closed. Memory was reclaimed on closing the window. I turned off all memory caching in Opera user prefs for this test. I'm not an Opera user, so am just getting familiar with all their config stuff for this test. As I understand the docs, this method takes priority over any opera:config setting, etc.īut, I tend to agree that there's some Opera optimization going on here. Per the support docs I tried setting tOverrideHistoryNavigationMode='compatible' in my JS, but it didn't change anything. The support link didn't directly help, but it got me thinking (always a good thing). Am I doing something wrong here? Or is this a known Opera issue? ![]() I had hoped this was a no-brainer test that all browsers would pass, so I could move on to more "interesting" conditions. But regardless of reload, memory never goes back down below the initial load spike. In Opera, memory spikes on load, and seems to also spike further on each reload (but not always.). In FF and Safari reloading the page does not use any further memory, and all memory is returned when the window (tab) is closed. Memory usage spikes up on page load, as expected. I monitor the memory usage using 'top' on Mac 10.4.11. As you can see this is simple JS, no circular DOM links, no closures. I shouldn't need the cleanup() call on window.unload, but tried that also. But Opera just takes memory and never gives it back. ![]() ![]() I've started with a fairly simple test, and can confirm no memory leaks in Firefox and Safari. Currently I'm only testing FF 3.6, Opera 10.10, and Safari 4.0.3. It also provides all the latest security and performance enhancements for Internet Explorer 5 for Mac OS X.I am trying to figure out certain memory leak conditions in javascript on a few browsers. This latest version - version 5.2.3 - enhances browser compatibility for users who work on a network with secure authentication or with proxy servers. If you've just switched from Windows to Mac, try one of the browsers suggested above instead. There are absolutely no compelling reasons to use Internet Explorer for Mac. Since development finished in 2005, Internet Explorer for Mac doesn't offer even the most basic features that you would consider a prerequisite on any browser nowadays like tabs, extensions, saved sessions or private data management. Internet Explorer for Mac is incredibly slow, buggy, prone to crashes and freezing and is woefully short of security settings. We couldn't even render the Softonic website in it and indeed, most websites failed to load properly. However, for normal internet browsing we'd really discourage you from using it. However, if you really can't help yourself and are an Internet Explorer nostalgic, you might want to try it for a trip down memory lane. Alternatively, just check out all of the other browsers available for Mac. Since the browser is no longer designed to handle the requirements of most modern web pages, we strongly advise you to try Firefox, Chrome, Safari or Opera instead. Microsoft ended support for Internet Explorer for Mac on December 31st, 2005, and does not provide further security or performance updates. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |