[whpalmer4]

All of the mentioned pages appear to load okay for me when done in a newly-opened copy of OmniWeb. When OmniWeb runs out of address space, it often behaves similarly to what you describe; are you using a workspace that has lots of tabs and windows open? Next time, when it freezes, before force-quitting the app, use the Activity Monitor to select the OmniWeb process, click on the Inspect button, and the Memory section in the resulting window. See what it reports for Virtual Memory Size. If that number is 3.95 GB or larger, you have run out of address space. Loading pages with "complicated" content chews through the address space faster than simpler pages that aren't monuments to how clever the web designer is...

I would try launching OmniWeb in a new workspace (hold down the shift key when launching it) and visiting those pages. I think there's a good chance they will work properly, but if they don't, you've narrowed the problem down a bit.