I am moving this to MAC support since the Bug Report forum couldn't help.
Original thread is here.
The following actions cause the Unity Player to freeze instantly:
Speedstrike attaches to any Hero
Moonstalker activates his Shadow ability
Blood Frenzy attaches to any Hero
- It happens during Challenge play, AI play, and on replay
- It happens if either my opponent or I take the action
CrashReporter details:
1)
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 16
...
Thread 16 Crashed:
0 libSystem.B.dylib 0x96ef02ac __semwait_signal_nocancel + 8
1 libSystem.B.dylib 0x96eefd78 nanosleep$NOCANCEL$UNIX2003 + 176
2 libSystem.B.dylib 0x96ee8fdc usleep$NOCANCEL$UNIX2003 + 68
3 libSystem.B.dylib 0x96f02b9c __abort + 88
4 libSystem.B.dylib 0x96f02c04 abort + 96
5 libSystem.B.dylib 0x96ed1fe8 internal_catch_exception_raise + 116
6 libSystem.B.dylib 0x96ebe400 _Xexception_raise + 260
7 libSystem.B.dylib 0x96ebe2a4 exc_server + 164
8 com.OverTheEdge.MonoBundle 0x19fb2870 catch_exception_raise + 128
2)
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 17
....
Thread 17 Crashed:
0 libSystem.B.dylib 0x96ef02ac __semwait_signal_nocancel + 8
1 libSystem.B.dylib 0x96eefd78 nanosleep$NOCANCEL$UNIX2003 + 176
2 libSystem.B.dylib 0x96ee8fdc usleep$NOCANCEL$UNIX2003 + 68
3 libSystem.B.dylib 0x96f02b9c __abort + 88
4 libSystem.B.dylib 0x96f02c04 abort + 96
5 libSystem.B.dylib 0x96ed1fe8 internal_catch_exception_raise + 116
6 libSystem.B.dylib 0x96ebe400 _Xexception_raise + 260
7 libSystem.B.dylib 0x96ebe2a4 exc_server + 164
8 com.OverTheEdge.MonoBundle 0x14a45870 catch_exception_raise + 128
Troubleshooting steps taken:
- Completely deleted previous Unity packages and configuration files at each step .
- Installed the Unity player from Unity3d Website
- Created a new user with Admin priveleges in Leopard. Installed new Unity player
- Reconfigured RAM modules, moving them into different slots, and removed the single mismatched 256MB DIMM
- Tested game on Camino, Opera, Safari, and Firefox browsers
- Rebooted into OSX Tiger 10.4.11 and tested on Camino, Safari, and Opera browsers
None of the actions taken above have made any change to the symptoms. The Unity player consistently makes libSystem.B.dylib call into unmapped memory at the exact same location (0x96ef02ac). Note that OSX Tiger and Leopard use different versions of libSystem.B.dylib:
Tiger version 88.0.0
Leopard version 111.1.4
Question: Can using the libSystem.B_debug.dylib help me narrow down the problem, or is Moonbundle just making bad memory calls?
System:
PowerMAC G4 Dual 1.33GHz, 1.75GB RAM
OSX 10.4.11 Tiger
OSX 10.5.8 Leopard
Bookmarks