Author Topic: Mac OS X crashes  (Read 893 times)

So lately a decent amount of servers have been crashing me for no apparent reason. At first I thought it was a certain add-on, but then I noticed the game crashing at "Loading datablocks". So I'm confused. If anyone here knows how to read this crash report or how to do something about it, please tell me. I'm not expecting much though.

Code: [Select]
Process:         Blockland [586]
Path:            /Users/Carlo/Desktop/Blockland v14/Blockland.app/Contents/MacOS/Blockland
Identifier:      org.step1.blockland
Version:         1.0.3 ©2007 Step 1: Games LLC (13m)
Code Type:       X86 (Native)
Parent Process:  launchd [99]

Date/Time:       2010-02-13 07:50:36.478 -0800
OS Version:      Mac OS X 10.6 (10A432)
Report Version:  6

Interval Since Last Report:          361308 sec
Crashes Since Last Report:           103
Per-App Interval Since Last Report:  169864 sec
Per-App Crashes Since Last Report:   31
Anonymous UUID:                      689A11F2-3826-4EF0-8086-61562520AFCC

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000034
Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
0   libSystem.B.dylib              0xffff0633 __bzero + 51
1   org.step1.blockland            0x002d9981 0x1000 + 2984321
2   org.step1.blockland            0x002f2d29 0x1000 + 3087657
3   org.step1.blockland            0x002f324c 0x1000 + 3088972
4   org.step1.blockland            0x000a7d40 0x1000 + 683328
5   org.step1.blockland            0x000a7e85 0x1000 + 683653
6   org.step1.blockland            0x002f71d2 0x1000 + 3105234
7   org.step1.blockland            0x0014759e 0x1000 + 1336734
8   org.step1.blockland            0x0014b22f 0x1000 + 1352239
9   org.step1.blockland            0x0027bf7b 0x1000 + 2600827
10  org.step1.blockland            0x00275d4e 0x1000 + 2575694
11  org.step1.blockland            0x0014a3ac 0x1000 + 1348524
12  org.step1.blockland            0x0027684c 0x1000 + 2578508
13  org.step1.blockland            0x0009f30f 0x1000 + 647951
14  org.step1.blockland            0x00279cdc 0x1000 + 2591964
15  org.step1.blockland            0x00284084 0x1000 + 2633860
16  org.step1.blockland            0x0023d20b 0x1000 + 2343435
17  org.step1.blockland            0x0015758d 0x1000 + 1402253
18  org.step1.blockland            0x00245c9a 0x1000 + 2378906
19  com.apple.CoreFoundation      0x963bceee __CFRunLoopRun + 6846
20  com.apple.CoreFoundation      0x963bad34 CFRunLoopRunSpecific + 452
21  com.apple.CoreFoundation      0x963bab61 CFRunLoopRunInMode + 97
22  com.apple.HIToolbox            0x917c4fec RunCurrentEventLoopInMode + 392
23  com.apple.HIToolbox            0x917c4cdf ReceiveNextEventCommon + 158
24  com.apple.HIToolbox            0x9194ccde _AcquireNextEvent + 54
25  com.apple.HIToolbox            0x91942a20 RunApplicationEventLoop + 228
26  org.step1.blockland            0x002441da 0x1000 + 2372058
27  org.step1.blockland            0x000296da 0x1000 + 165594

Thread 1:  Dispatch queue: com.apple.libdispatch-manager
0   libSystem.B.dylib              0x9820e10a kevent + 10
1   libSystem.B.dylib              0x9820e824 _dispatch_mgr_invoke + 215
2   libSystem.B.dylib              0x9820dce1 _dispatch_queue_invoke + 163
3   libSystem.B.dylib              0x9820da86 _dispatch_worker_thread2 + 234
4   libSystem.B.dylib              0x9820d511 _pthread_wqthread + 390
5   libSystem.B.dylib              0x9820d356 start_wqthread + 30

Thread 2:
0   libSystem.B.dylib              0x9821582a __semwait_signal + 10
1   libSystem.B.dylib              0x98241681 nanosleep$UNIX2003 + 188
2   libSystem.B.dylib              0x982415bf usleep$UNIX2003 + 61
3   org.step1.blockland            0x0023132c 0x1000 + 2294572
4   org.step1.blockland            0x0023138c 0x1000 + 2294668
5   libSystem.B.dylib              0x98214fe1 _pthread_start + 345
6   libSystem.B.dylib              0x98214e66 thread_start + 34

Thread 3:
0   libSystem.B.dylib              0x9821582a __semwait_signal + 10
1   libSystem.B.dylib              0x982154e6 _pthread_cond_wait + 1191
2   libSystem.B.dylib              0x98217178 pthread_cond_wait$UNIX2003 + 73
3   org.step1.blockland            0x005027ac 0x1000 + 5248940
4   org.step1.blockland            0x0043e4b5 0x1000 + 4445365
5   org.step1.blockland            0x0050283c 0x1000 + 5249084
6   libSystem.B.dylib              0x98214fe1 _pthread_start + 345
7   libSystem.B.dylib              0x98214e66 thread_start + 34

Thread 4:
0   libSystem.B.dylib              0x981e795a semaphore_timedwait_signal_trap + 10
1   libSystem.B.dylib              0x98215469 _pthread_cond_wait + 1066
2   libSystem.B.dylib              0x98244268 pthread_cond_timedwait_relative_np + 47
3   com.apple.audio.CoreAudio      0x93f07ec1 CAGuard::WaitFor(unsigned long long) + 219
4   com.apple.audio.CoreAudio      0x93f0aef3 CAGuard::WaitUntil(unsigned long long) + 289
5   com.apple.audio.CoreAudio      0x93f087f0 HP_IOThread::WorkLoop() + 1892
6   com.apple.audio.CoreAudio      0x93f08087 HP_IOThread::ThreadEntry(HP_IOThread*) + 17
7   com.apple.audio.CoreAudio      0x93f07f9e CAPThread::Entry(CAPThread*) + 140
8   libSystem.B.dylib              0x98214fe1 _pthread_start + 345
9   libSystem.B.dylib              0x98214e66 thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0x00000000  ebx: 0x00000000  ecx: 0x00000018  edx: 0x00000006
  edi: 0x00000034  esi: 0x00000001  ebp: 0xbfffd778  esp: 0xbfffd774
   ss: 0x0000001f  efl: 0x00010206  eip: 0xffff0633   cs: 0x00000017
   ds: 0x0000001f   es: 0x0000001f   fs: 0x00000000   gs: 0x00000037
  cr2: 0x00000034




Thanks.

You signed on for this bullstuff when you bought a Macintosh.

 :cookieMonster:

So in essence you can't read code for jack stuff and you came only to post a quote that everyone has seen hundreds of times?

You're a moron if you think crashes are native only to MAC OS X, and that's exactly what your post, and Badspot's imply. Crashes are visible, and in my opinion of using XP for a decade, much more occurrent.
« Last Edit: February 13, 2010, 11:11:51 AM by Hysterio »

So in essence you can't read code for jack stuff and you came only to post a quote that everyone has seen hundreds of times?

You're a moron if you think crashes are native only to MAC OS X, and that's exactly what your post, and Badspot's imply. Crashes are visible, and in my opinion of using XP for a decade, much more occurrent.
This isn't code, Coding help is for like
functions
Commands
And all that stuff,
Most likely you have a add-on or something messing this up
Or, wrong version of blockland.

So in essence you can't read code for jack stuff and you came only to post a quote that everyone has seen hundreds of times?

Yup.

This isn't code, Coding help is for like
functions
Commands
And all that stuff,
Most likely you have a add-on or something messing this up
Or, wrong version of blockland.
Thanks for the advice.
I could be an add-on, but it's definitely not the wrong version because I wouldn't be able to play online otherwise.

I have this problem too, it's usually caused by poorly packaged models for weapons and vehicles that cause it. Since RTB has no Mac testers, these addons enter the mainstream despite being broken.