Originally Posted by Mad Hatter
Buy more memory? How much do you have? I would guess that 1.5GB should be pretty normal for most use. Definitely more than the "minimums" of 512MB or so. And more for G5s even than G4 systems (no idea what MacIntel but suspect that Rosetta likes to have plenty!).
I have 1.75GB and almost never see more than one swap file - for some reason installing one piece of software created a couple on another system with only 1GB - I keep a window on the desktop to /private/var/vm when I want to know.
You might want to boot into Single User Mode and check your disk if it got too full, then, if you have Applejack, run that and remove all the cache folders and swap files - best way I know - as well as backup and make more room or get a new drive.
Thanks for volunteering some help, but I don't need any as I was working with UNIX when AT&T still owed it ;)
I would rather Omni searched for (and cured) the cause, than users suggest how to put up with the symptoms.
NB: I deliberately have CRASHREPORTER=-NO- in /etc/hostconfig and kern.coredump=0 in /etc/sysctl.conf
I have this from a JavaNativeCrash log with the example described earlier:
Unknown Signal (13): SIG_IGN, sa_mask=0x00000000, sa_flags=0x00000002
Unknown Signal (30): [OmniCrashCatcher+0x1fb0], sa_mask=0x00000000, sa_flags=0x00000040
Unknown Signal (31): SIG_DFL, sa_mask=0x00000000, sa_flags=0x00000002
Unknown Signal (1): [libjvm.dylib+0x2866a4], sa_mask=0xfffefeff, sa_flags=0x00000002
Unknown Signal (2): [libjvm.dylib+0x2866a4], sa_mask=0xfffefeff, sa_flags=0x00000002
Unknown Signal (3): [libjvm.dylib+0x2866a4], sa_mask=0xfffefeff, sa_flags=0x00000002
Unknown Signal (15): [libjvm.dylib+0x2866a4], sa_mask=0xfffefeff, sa_flags=0x00000002
As I write SP7 has just crashed again, spontaneously:
Process: OmniWeb (5.5 sneaky peek 7 (v578) (Apr 27 2006))
exception = 0x00000001, code = 0x00000001;0x10965000;
This time I have an OmniCrash report to send in :) what fun.
From a commercial point of view any requirement to have N Gb of memory for a browser is going to be a barrier to sales. If this product wants to sell to the largest possible number of Mac users then it needs to manage to run within the system requirements of the OS (which are more than sufficient to support a browser).
For those with low memory systems that like to see their browser fail, here's another candidate http://www.milliondollarhomepage.com/
Once again, my advice to Omni is for QA to test on low end Macs as shipped.