Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'OmniWeb 5 performance' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
OmniWeb 5 performance
Authored by: ddldreaming on Sep 08, '04 03:07:42PM

I've been using the OmniWeb demo for the past couple of weeks, and while I adore many of its features, it's got some performance problems that make me wary of sticking with it. It uses noticeably more memory than Mozilla or Safari do for the same pages, and doesn't appear to free it as quickly. It also sometimes starts pegging the CPU for no reason (I think most often after rendering a MapQuest or MacUpdate page). When this happens the only remedy is to quit and reload (closing the suspect pages doesn't help). Has anyone else seen this sort of problem crop up?

Of course, when I do need to quit, or when it crashes, its workspace-preservation features are a godsend!

To its credit, Omni has a dedicated team who respond to their customers; when I sent a note about my concerns I got a quick reply from Troy suggesting that v5.1 (with its newer WebCore) may address these issues.



[ Reply to This | # ]