Closed GoogleCodeExporter closed 9 years ago
What steps will reproduce the problem? 1. Click on a magnet link - Transmission-remote-gui picks it up 2. Specify a destination other that /User/<username>/Downloads 3. Transmission crashes. Transmission-remote-gui must be restarted to connect to a new instance of Transmission. What is the expected output? What do you see instead? The torrent added and downloading to the specified directory. From Transmission: "Transmission quit unexpectedly. Click reopen to open the application again..." The abbreviated stack dump is included below. From Trans-remote-gui: "JSON element 'torrent-added' not found." If I attempt to connect after re-starting Transmission: "Access violation". After quitting Trans-remote-gui and starting it again, it connects fine. What version of the product are you using? On what operating system? Macbook - Transmission Remote GUI - 4.1 iMac - Transmisison - 2.81 (14128) Please provide any additional information below. Process: Transmission [5175] Path: /Applications/Transmission.app/Contents/MacOS/Transmission Identifier: org.m0k.transmission Version: 2.81 (14128) Code Type: X86-64 (Native) Parent Process: launchd [141] User ID: 501 Date/Time: 2013-07-23 09:55:23.104 -0700 OS Version: Mac OS X 10.8.4 (12E55) Report Version: 10 Interval Since Last Report: 66879 sec Crashes Since Last Report: 5 Per-App Interval Since Last Report: 5636 sec Per-App Crashes Since Last Report: 5 Anonymous UUID: E5144276-903B-0108-8689-21616D978A55 Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000060 VM Regions Near 0x60: --> __TEXT 0000000100000000-00000001000f9000 [ 996K] r-x/rwx SM=COW /Applications/Transmission.app/Contents/MacOS/Transmission Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 org.m0k.transmission 0x000000010002394f 0x100000000 + 145743 1 org.m0k.transmission 0x000000010002bae2 0x100000000 + 178914 2 org.m0k.transmission 0x000000010002b581 0x100000000 + 177537 3 org.m0k.transmission 0x000000010002a2fd 0x100000000 + 172797 ... Thread 1:: Dispatch queue: com.apple.libdispatch-manager 0 libsystem_kernel.dylib 0x00007fff85290d16 kevent + 10 1 libdispatch.dylib 0x00007fff8a668dea _dispatch_mgr_invoke + 883 2 libdispatch.dylib 0x00007fff8a6689ee _dispatch_mgr_thread + 54 Thread 2: 0 libsystem_c.dylib 0x00007fff87e6888b free + 90 1 org.m0k.transmission 0x00000001000744e1 0x100000000 + 476385 2 org.m0k.transmission 0x000000010007bc2b 0x100000000 + 506923 ... Thread 3: 0 libsystem_kernel.dylib 0x00007fff85290386 __semwait_signal + 10 ... Thread 4:: com.apple.CFSocket.private 0 libsystem_kernel.dylib 0x00007fff85290322 __select + 10 1 com.apple.CoreFoundation 0x00007fff82632f46 __CFSocketManager + 1302 2 libsystem_c.dylib 0x00007fff87e4f7a2 _pthread_start + 327 3 libsystem_c.dylib 0x00007fff87e3c1e1 thread_start + 13 Thread 5: 0 libsystem_kernel.dylib 0x00007fff852906d6 __workq_kernreturn + 10 1 libsystem_c.dylib 0x00007fff87e51f4c _pthread_workq_return + 25 2 libsystem_c.dylib 0x00007fff87e51d13 _pthread_wqthread + 412 3 libsystem_c.dylib 0x00007fff87e3c1d1 start_wqthread + 13 Thread 6: 0 libsystem_kernel.dylib 0x00007fff852906d6 __workq_kernreturn + 10 1 libsystem_c.dylib 0x00007fff87e51f4c _pthread_workq_return + 25 2 libsystem_c.dylib 0x00007fff87e51d13 _pthread_wqthread + 412 3 libsystem_c.dylib 0x00007fff87e3c1d1 start_wqthread + 13 Thread 7: 0 libsystem_kernel.dylib 0x00007fff852906d6 __workq_kernreturn + 10 1 libsystem_c.dylib 0x00007fff87e51f4c _pthread_workq_return + 25 2 libsystem_c.dylib 0x00007fff87e51d13 _pthread_wqthread + 412 3 libsystem_c.dylib 0x00007fff87e3c1d1 start_wqthread + 13 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000000 rbx: 0x0000000109055c50 rcx: 0x4072700000000000 rdx: 0x00000001017e4c30 rdi: 0x0000000100cb4c08 rsi: 0x00000001000b9b04 rbp: 0x00007fff5fbfb730 rsp: 0x00007fff5fbfb730 r8: 0x0000000101091150 r9: 0x00000000e7ea8aab r10: 0x00000001007e0100 r11: 0x000000010085fd70 r12: 0x00007fff5fbfb900 r13: 0x00007fff88eca240 r14: 0x00000001010289d0 r15: 0x00007fff88eca240 rip: 0x000000010002394f rfl: 0x0000000000010246 cr2: 0x0000000000000060 Logical CPU: 1 Binary Images: 0x100000000 - 0x1000f8fff +org.m0k.transmission (2.81 - 14128) <483FBD54-3151-3FDD-92AC-9897B9F03C0A> /Applications/Transmission.app/Contents/MacOS/Transmission 0x10012e000 - 0x100145fff +org.andymatuschak.Sparkle (1.5 Beta [bzr] - 337) <8BE62C95-BF56-8320-646F-385AC5F1D513> /Applications/Transmission.app/Contents/Frameworks/Sparkle.framework/Versions/A/Sparkle 0x10015f000 - 0x10018efff +com.growl.growlframework (1.3.1 - 1.3.1) <81F2E452-20C8-3F2D-94B2-B58FA5DE1ECE> /Applications ... External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 11 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 808 thread_create: 1 thread_set_state: 0 VM Region Summary: ReadOnly portion of Libraries: Total=208.7M resident=98.5M(47%) swapped_out_or_unallocated=110.2M(53%) Writable regions: Total=115.6M written=17.8M(15%) resident=42.1M(36%) swapped_out=0K(0%) unallocated=73.5M(64%) REGION TYPE VIRTUAL =========== ======= CG backing stores 1076K CG image 1040K CG raster data 88K CG shared images 1216K CoreImage 72K CoreServices 1172K IOKit 4984K IOKit (reserved) 320K reserved VM address space (unallocated) MALLOC 82.7M MALLOC guard page 48K MALLOC_LARGE (reserved) 128K reserved VM address space (unallocated) Memory tag=240 4K Memory tag=242 12K Memory tag=243 4K Memory tag=251 28K OpenCL 40K STACK GUARD 56.0M Stack 11.1M VM_ALLOCATE 16.4M __DATA 17.9M __IMAGE 528K __LINKEDIT 53.2M __TEXT 155.6M __UNICODE 544K mapped file 49.3M shared memory 16.0M =========== ======= TOTAL 469.2M TOTAL, minus reserved VM space 468.7M
Original issue reported on code.google.com by travisis...@gmail.com on 23 Jul 2013 at 5:05
travisis...@gmail.com
It's clearly the Transmission bug. Proably it is alrasy fixed in the latest version.
Original comment by j...@cp-lab.com on 28 Aug 2013 at 1:43
j...@cp-lab.com
Original issue reported on code.google.com by
travisis...@gmail.com
on 23 Jul 2013 at 5:05