Prior to Leopard I don't recall any times where Parallels suddenly quits. I'm running Parallels 2.5 (3224) on Leopard. I have a need to use Parallels once a week and since Leopard I have an unexpected crash almost every week. Sometimes there is no crash. When there is, I just restart Parallels. I'm running WinXP with 512megs of memory, shared networking, image is 8GB with 2.8 free. All I run is cisco vpn, AIM, email, and IE. So, nothing I consider odd. At the times of a crash, I'm either just typing or pasting some text - and POOF, parallels is gone followed by "parallels has unexpectedly quit". All I have (or know to get) is the crash from the Console log and then the error log mentioned in the Console log. 2/29/08 10:05:32 AM [0x0-0x196196].com.parallels.desktop[4780] Parallels Desktop 2.5 critical error! Send log file ( /Library/Parallels/bugreports/parallels-fault-100532.290108.4780.log ) to [email protected] 2/29/08 10:05:36 AM kernel [err in VmObserverThread ] : Forced quit VM (!) id=188334864 -> ../host.Darwin/device.c:416 2/29/08 10:05:37 AM ReportCrash[4929] Formulating crash report for process Parallels[4780] 2/29/08 10:05:39 AM ReportCrash[4929] Saved crashreport to /Users/zzzzz/Library/Logs/CrashReporter/Parallels_2008-02-29-100532_zzzzz-computer.crash using uid: 501 gid: 501, euid: 501 egid: 501 2/29/08 10:05:38 AM com.apple.launchd[156] ([0x0-0x196196].com.parallels.desktop[4780]) Exited abnormally: Segmentation fault This is the log file mentioned above ------------------------------------------------------------------------------- Parallels Desktop 2.5 for Mac OS X version 2.5 Build 3224.0 from 2007-12-19 ------------------------------------------------------------------------------- Received SIGSEGV: Segmentation fault Access to fault address: 0x1c2af000 unknown signal sender: 1 ------------------------------------------------------------------------------- I found 1 thread that suggests disabling the Virtual Memory Preallocation, but from a quick search, that's the only thread and I can't find where to set or unset that. Any other suggestions? Should I just buy the v3.0 ? I have a feeling that even with the 2.5 leopard update back in December I think that maybe I'm not truly Leopard compatible. Thanks.
