Ubuntu
transmission package

transmission crashed with SIGSEGV in tr_torrentFindFromId()

Bug #441481 reported by ZRDX on 2009-10-03

This bug report is a duplicate of: Bug #319880: Crashes on shutdown if libevent loop doesn't exit soon enough. Edit Remove

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	transmission (Ubuntu)	Incomplete	Medium	Unassigned

Bug Description

Binary package hint: transmission

ProblemType: Crash
Architecture: i386
Date: Sat Oct 3 19:35:21 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/transmission
Package: transmission-gtk 1.75-0ubuntu1
ProcCmdline: transmission
ProcEnviron:
LANGUAGE=en_GB.UTF-8
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
Segfault happened at: 0x8098760 <tr_torrentFindFromId+32>: cmp %esi,0x508(%eax)
PC (0x08098760) ok
source "%esi" ok
destination "0x508(%eax)" (0x00000554) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
tr_torrentFindFromId ()
?? ()
?? ()
event_base_loop () from /usr/lib/libevent-1.4.so.2
event_loop () from /usr/lib/libevent-1.4.so.2
Title: transmission crashed with SIGSEGV in tr_torrentFindFromId()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

ZRDX (zrdx-spb) wrote on 2009-10-03:

Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (877 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (33.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (765 bytes, text/plain; charset="utf-8")
Registers.txt Edit (477 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (737 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (8.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-10-05: Stacktrace.txt (retraced)

Stacktrace.txt (retraced) Edit (1.0 KiB, text/plain)

StacktraceTop:tr_torrentFindFromId (session=0x9e59260, id=2) at torrent.c:64
onStoppedResponse (session=0x9e59260, responseCode=0,
tr_multi_perform (g=0x9e7d8c0, fd=<value optimized out>)
event_base_loop (base=0x9e58708, flags=0) at event.c:392
event_loop (flags=0) at event.c:468

Revision history for this message

Apport retracing service (apport) wrote on 2009-10-05: ThreadStacktrace.txt (retraced)

ThreadStacktrace.txt (retraced) Edit (13.3 KiB, text/plain)

Changed in transmission (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Krzysztof Klimonda (kklimonda) on 2009-10-05

visibility:

private → public

Revision history for this message

Charles Kerr (charlesk) wrote on 2009-10-08:

> #0 tr_torrentFindFromId (session=0x9e59260, id=2) at torrent.c:64
> tor = (tr_torrent *) 0x4c

That 0x4c looks awfully suspicious to me.

Revision history for this message

Charles Kerr (charlesk) wrote on 2009-10-10:

ZRDX: what were you doing when this happened? Did this happen while exiting Transmission?

Revision history for this message

Charles Kerr (charlesk) wrote on 2009-10-10:

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Revision history for this message

Charles Kerr (charlesk) wrote on 2009-10-26:

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Krzysztof Klimonda (kklimonda) on 2009-10-30

Changed in transmission (Ubuntu):
status:	New → Incomplete

Revision history for this message

Goran Molnar (goran-molnar) wrote on 2009-11-02:

This bug happened to me when i quit Transmission, after it was up for a long time (approx. 32 hours).
I havent managed to reproduce it, after quitting it again for a few times it closed properly.

Revision history for this message

Charles Kerr (charlesk) wrote on 2009-11-10:

Goran, thanks for pointing out that this was happening at shutdown.

This particular bug is a duplicate of bug 319880, so it is being marked as such. Any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.