This is a consequence of OmniWeb being multi-threaded - sometimes one of the threads will crash (and hence CrashCatcher will launch), but it doesn't affect the front-most window or the whole app. Therefore, it seems that OmniWeb hasn't crashed, whereas it actually has (for example if you try to continue browsing, it will eventually lock up completely or crash completely).

[QUOTE=JKT]This is a consequence of OmniWeb being multi-threaded - sometimes one of the threads will crash (and hence CrashCatcher will launch), but it doesn't affect the front-most window or the whole app. Therefore, it seems that OmniWeb hasn't crashed, whereas it actually has (for example if you try to continue browsing, it will eventually lock up completely or crash completely).[/QUOTE]
In general, when OmniWeb crashes like this with the CrashCatcher in front, OmniWeb remains plainly usable, if you have a text field, you can continue to fill in, or browse a page, but, if you valid the CrashCatcher, then OmniWeb stops and leaves ...
And it is what happen in this thread all the time, that's why it is boring, because the browser looks to work.

It remains usable for the front-most window, but if you try to access other tabs or click links to open other sites, it will [I]typically[/I] freeze or crash outright. The reason being that the thread which initially crashed and caused CrashCatcher to launch was one that a background tab or window instigated, not the tab/window you are currently in.