This particular issue is not common to other browsers. There is a known issue related to JavaScript and OmniWeb. When scripts are running and a window is closed, the script doesn't stop. This is unlike other browsers. It causes OW to eat up more and more CPU cycles.
When this happens, it can take up to several minutes for OW to quit - if it quits at all. Sometimes it just crashes. Then it can take a minute or so to reload depending on how many windows you have open.
They have made progress on this, and at last check it will be released as 5.6.
Last I heard, there aren't any memory leaks in OW.
When this happens, it can take up to several minutes for OW to quit - if it quits at all. Sometimes it just crashes. Then it can take a minute or so to reload depending on how many windows you have open.
They have made progress on this, and at last check it will be released as 5.6.
Last I heard, there aren't any memory leaks in OW.