Parallels 4128 Crashes

   By chris on June 26th 2007 in /dev/random | 601 views

Seems Parallels 3 build 4128 crashes far more frequently than previous builds. Fortunately OS X generates crash logs when it happens. To the Parallels folks: I’m sure users would be happy to send their crash logs to you to help trouble-shoot or verify the problem but you need to provide a means.

Emailing support@parallels.com gets rejected, submitting the crash report via the Parallels support form at http://www.parallels.com/support/p,2? gets refused, so if you’re interested, contact me directly and I’ll pass it along.

In the meantime, here’s the interesting bits:

Exception: EXC_BAD_ACCESS (0×0001)
Codes: KERN_INVALID_ADDRESS (0×0001) at 0×01d4a000
…
Thread 11 Crashed:
0 <<00000000>> 0xffff0af5 __memcpy + 853 (cpu_capabilities.h:228)
1 com.parallels.desktop 0×0076c173 0×1000 + 7778675
2 com.parallels.desktop 0×00659fdf 0×1000 + 6655967
3 com.parallels.desktop 0×0096b69b QList::append(TGDev
const&) + 379
4 com.parallels.desktop 0×00725401 0×1000 + 7488513
5 libSystem.B.dylib 0×90024227 _pthread_body + 84
…
Thread 11 crashed with X86 Thread State (32-bit):
eax: 0xffff0ab7 ebx: 0×00659ea0 ecx: 0×0000003a edx: 0xfffff900
edi: 0×01d4a700 esi: 0×1c43edc6 ebp: 0xb0811e88 esp: 0xb0811e80
ss: 0×0000001f efl: 0×00010286 eip: 0xffff0af5 cs: 0×00000017
ds: 0×0000001f es: 0×0000001f fs: 0×0000001f gs: 0×00000037

2 Responses to “Parallels 4128 Crashes”

  1. maco responded on 13 Jul 2007 at 9:00 pm #

    Having similar problems. Has support helped at all?

  2. chris responded on 15 Jul 2007 at 3:23 pm #

    They have been wholly silent, both here (though I don’t suspect they read this) and - and more distressingly - on the Parallels support forums (http://forums.parallels.com). The most said about any issues is that a next version will be coming out “within a few weeks”.

    I await with bated breath.

Trackback URI | Comments RSS

Leave a Reply