[Ward]

OmniWeb is currently idling with a single, blank page open in my default workspace (no pages saved).

I've been checking Activity Monitor for the past 10 minutes -- OmniWeb is consuming a solid 18-21% of the CPU ... doing nothing.

[Several minutes later: When I quit and relaunched OmniWeb, the CPU load dropped to 0.00%.]

[copy of my formal bug report]

[Len Case]

Next time this happens--would you please try typing the following command in a terminal window:

sample OmniWeb 2

it will then capture what OmniWeb is doing every 10ms for the next 2 seconds and write a file

Sampling process 10922 each 10 msecs 200 times
Sample analysis of process 10922 written to file /tmp/OmniWeb_10922.sample.txt

Please then send feedback (Help->Send Feedback) and include the file.

To include the file in mail quickly, click the attach button and when the open sheet comes up, type a '/'. The "Go To Folder" dialog will pop up and you can finish typing "tmp" and hit return to go straight there.

[Forrest]

Let me know how you do this, Ward. It's a great tip. I can't seem to get mine below 70% - 20% would be killer.

;)

[philonous]

I have experienced this also. There was one time when my PB's fan would not go off. Activity Monitor reported that OW was using 20% of CPU, even though I had no pages open. After restarting OW, it went back to 0.

I will try to report it next time I notice it.

[gumby]

After years of this bothering me I have decided it's likely a javascript problem. Specifically: if I visit a page with lots of js perhaps it loads something into OW which can't unload it when the page is no longer around. Thus restarting, which doesn't load the offending page, is a "cold boot" GC.

It could be some other plug-in (flash sucks pretty hard too). The reason I think it's JS is that I mostly have JS disabled except for certain pages. It seems to happen when I have visited those pages.

But I don't know the internal architecture of OW so this is a black-box analysis. So don't treat it as any kind of massively-researched gospel!!

[JKT]

From what I have seen in other threads from OmniGroup personnel, this is linked to Javascript and/or garbage collection (whatever that is). I'm hoping that they get it fixed before 5.5 final (preferably for the next beta would be nice!) as this issue has been really annoying to me ever since the first sneakypeek.