OmniWeb 4.1sp3 appears to be out, at the same place as 4.1sp1. I don't know of any improvements per say, but it seems faster.
I didn't find out about it this way, anyway. I just have OmniWeb check every twelve hours to see if the Sneaky Peak directory has changed.Subject: OmniWeb 4.1 sneaky peek 3 is now available
From: Ken Case
You'll find OmniWeb 4.1 sneaky peek 3 at http://www.omnigroup.com/ftp/pub/outgoing/sneakypeek/ .
improvements. This problem is fixed in sp3.
(We haven't fixed the big leak yet, nor the reload problem--we haven't forgotten about them, and we'll fix them before we release 4.1 beta 1, but in these first few sneaky peek releases we're mostly focused on extending our compatibility and getting development builds out to you quickly so you can give us feedback.)
The memory leak has been pretty obvious to me in OmniWeb 4.1 sp3. If you keep the ProcessViewer open or use the top command in the Terminal and start browsing the web, it builds up pretty fast. OmniWeb usually opens on my machine taking up about 2.3% of memory (I have 640MB ram), although will continue to climb by about .2% - .8% (depending on the size of the web site) with every new page loaded/reloaded. It's currently at 10.4% for me. Fortunately because of OS X's protected memory, this isn't too much of a problem... just quit OmniWeb and launch it again occasionally to clear up the memory.Originally posted by Red Phoenix
I still haven't encountered the memory leak, but I haven't left OmniWeb open for more than an hour. Now that every application opens so fast, I just have no need to leave most applications running all the time.