Member
2007-10-06, 05:48 AM
It is possible that you are experiencing the JS garbage collection bug that is in the version of WebKit that 5.5.4 is based upon, which causes OmniWeb to start sucking CPU cycles. The solution is to quit and restart OmniWeb or to download the 5.6 sneakypeek and use that instead.
Edit: However, the latest builds also have a serious bug that causes OmniWeb to hang at e.g. the apple store online.
Last edited by JKT; 2007-10-06 at 05:53 AM..