[I knew it was foolish to tempt fate by reporting SP4 was the Rock of Gibraltar. :o ]
For the second time since I started using SP5, ...
1. OmniWeb crashes.
2. CrashCatcher appears, and I fill in my report and send it.
3. OmniWeb remains on-screen, and I have to Force Quit to make it go away.
This time I noticed 100% CPU activity (via Cee Pee You). So I checked Activity Monitor, which showed OmniWeb and kernel_task each using 30-40% of the CPU, with kernel_task consuming 1.1 GB of virtual memory. After force quitting OmniWeb, kernel_task dropped back to its customary 4-7%.
For the second time since I started using SP5, ...
1. OmniWeb crashes.
2. CrashCatcher appears, and I fill in my report and send it.
3. OmniWeb remains on-screen, and I have to Force Quit to make it go away.
This time I noticed 100% CPU activity (via Cee Pee You). So I checked Activity Monitor, which showed OmniWeb and kernel_task each using 30-40% of the CPU, with kernel_task consuming 1.1 GB of virtual memory. After force quitting OmniWeb, kernel_task dropped back to its customary 4-7%.
Threaded Mode