I noticed that OmniWeb always starts up with a nice and low memory footprint. However once I've cycled through all tabs in all workspaces (that's what I usually do in the morning) memory usage increases depending on how many pages I have open across all workspaces.
The problem is that once the program has grabbed all that memory it never releases it again unless I close tabs (which is what I don't want, that's what the workspaces are for, aren't they?).
Why not allow it to automatically release memory for workspaces which haven't been in the foreground for a while? I would even sacrifice some runtime performance in allowing it to release memory as soon as I switch workspaces. That would make OmniWeb probably the leanest tabbed browser on earth.
Think about it!
The problem is that once the program has grabbed all that memory it never releases it again unless I close tabs (which is what I don't want, that's what the workspaces are for, aren't they?).
Why not allow it to automatically release memory for workspaces which haven't been in the foreground for a while? I would even sacrifice some runtime performance in allowing it to release memory as soon as I switch workspaces. That would make OmniWeb probably the leanest tabbed browser on earth.
Think about it!
Threaded Mode