New Build -- 2.10 (11294) -- unstable/crash happy

Ask for help and report issues not specific to either the Mac OS X or GTK+ versions of Transmission
Post Reply
oldstrega
Posts: 3
Joined: Sat Feb 27, 2010 8:27 pm

New Build -- 2.10 (11294) -- unstable/crash happy

Post by oldstrega »

not sure what the problem is. i have repaired disk permissions.

previous builds have been stable recently.
livings124
Transmission Developer
Posts: 3142
Joined: Fri Jan 13, 2006 8:08 pm

Re: New Build -- 2.10 (11294) -- unstable/crash happy

Post by livings124 »

oldstrega
Posts: 3
Joined: Sat Feb 27, 2010 8:27 pm

Re: New Build -- 2.10 (11294) -- unstable/crash happy

Post by oldstrega »

the crash report is quite lengthy but here it is. crashing like crazy this evening.

Process: Transmission [5382]
Path: /Volumes/Applications/Transmission.app/Contents/MacOS/Transmission
Identifier: org.m0k.transmission
Version: 2.10 (11294)
Code Type: X86-64 (Native)
Parent Process: launchd [220]

Date/Time: 2010-10-09 04:36:40.399 -0500
OS Version: Mac OS X 10.6.4 (10F569)
Report Version: 6

Interval Since Last Report: 218423 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 38072 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: CAF4B52D-4DA5-4D5C-A610-A0797D999341

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000020
Crashed Thread: 2

Thread 0: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x00007fff859a92fa mach_msg_trap + 10
1 libSystem.B.dylib 0x00007fff859a996d mach_msg + 59
2 com.apple.CoreFoundation 0x00007fff829603c2 __CFRunLoopRun + 1698
3 com.apple.CoreFoundation 0x00007fff8295f84f CFRunLoopRunSpecific + 575
4 com.apple.HIToolbox 0x00007fff8051c91a RunCurrentEventLoopInMode + 333
5 com.apple.HIToolbox 0x00007fff8051c71f ReceiveNextEventCommon + 310
6 com.apple.HIToolbox 0x00007fff8051c5d8 BlockUntilNextEventMatchingListInMode + 59
7 com.apple.AppKit 0x00007fff8178929e _DPSNextEvent + 708
8 com.apple.AppKit 0x00007fff81788bed -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155
9 com.apple.AppKit 0x00007fff8174e8d3 -[NSApplication run] + 395
10 com.apple.AppKit 0x00007fff817475f8 NSApplicationMain + 364
11 org.m0k.transmission 0x000000010000201f 0x100000000 + 8223
12 org.m0k.transmission 0x0000000100001f94 0x100000000 + 8084

Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x00007fff859c208a kevent + 10
1 libSystem.B.dylib 0x00007fff859c3f5d _dispatch_mgr_invoke + 154
2 libSystem.B.dylib 0x00007fff859c3c34 _dispatch_queue_invoke + 185
3 libSystem.B.dylib 0x00007fff859c375e _dispatch_worker_thread2 + 252
4 libSystem.B.dylib 0x00007fff859c3088 _pthread_wqthread + 353
5 libSystem.B.dylib 0x00007fff859c2f25 start_wqthread + 13

Thread 2 Crashed:
0 org.m0k.transmission 0x000000010006ba78 0x100000000 + 440952
1 org.m0k.transmission 0x000000010006bb85 0x100000000 + 441221
2 org.m0k.transmission 0x0000000100092b70 0x100000000 + 600944
3 org.m0k.transmission 0x0000000100083b2e 0x100000000 + 539438
4 org.m0k.transmission 0x0000000100081e64 0x100000000 + 532068
5 org.m0k.transmission 0x0000000100081499 0x100000000 + 529561
6 org.m0k.transmission 0x0000000100078ea3 0x100000000 + 495267
7 org.m0k.transmission 0x0000000100077e9e 0x100000000 + 491166
8 org.m0k.transmission 0x000000010009a726 0x100000000 + 632614
9 org.m0k.transmission 0x0000000100073834 0x100000000 + 473140
10 org.m0k.transmission 0x0000000100068ca0 0x100000000 + 429216
11 libSystem.B.dylib 0x00007fff859e2456 _pthread_start + 331
12 libSystem.B.dylib 0x00007fff859e2309 thread_start + 13
Jordan
Transmission Developer
Posts: 2312
Joined: Sat May 26, 2007 3:39 pm
Location: Titania's Room

Re: New Build -- 2.10 (11294) -- unstable/crash happy

Post by Jordan »

oldstrega, thanks very much for the crash report. That's a good first step. Next, could you repeat the process from a nightly build of Transmission? The dmg can be found at https://build.transmissionbt.com/job/trunk-mac/

This is possibly the same issue being discussed at viewtopic.php?f=4&t=10676&p=49691#p49625 but we won't know for sure without a nightly build's crash report.
Post Reply