transmission crashed with SIGSEGV in event_add()

[Socket]

Binary package hint: transmission

By ubuntu 9.10 Karmic Koala (beta?) - 22 Oct 2009

ProblemType: Crash
Architecture: i386
Date: Fri Oct 23 00:31:06 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/transmission
NonfreeKernelModules: nvidia
Package: transmission-gtk 1.75-0ubuntu2
ProcCmdline: transmission /home/username/.opera/temporary_downloads/Kniga.masterov.2009.TC.avi.torrent
ProcEnviron:
 LANGUAGE=ru_RU.UTF-8
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0xd5d450 <event_add+32>: mov 0x1c(%esi),%edi
 PC (0x00d5d450) ok
 source "0x1c(%esi)" (0x0000001c) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
 event_add () from /usr/lib/libevent-1.4.so.2
 tr_timerAdd ()
 event_base_loop () from /usr/lib/libevent-1.4.so.2
 event_loop () from /usr/lib/libevent-1.4.so.2
 event_dispatch () from /usr/lib/libevent-1.4.so.2
Title: transmission crashed with SIGSEGV in event_add()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:event_add (ev=0x0, tv=0xb767a218) at event.c:721
tr_timerAdd (timer=0x0, seconds=60, milliseconds=0)
event_base_loop (base=0x90c5a80, flags=0) at event.c:392
event_loop (flags=0) at event.c:468
event_dispatch () at event.c:406

[Charles Kerr (charlesk)]

Looks like the port forwarding timer got deleted. It's most likely that this happened during shutdown, but maybe there are other strange cases that could cause it, such as waking up after hibernation. In general this is harmless, but clearly we need to put a NULL pointer guard in for re-queueing the timer.

One-liner fix:

http://trac.transmissionbt.com/changeset/9441/

[Krzysztof Klimonda (kklimonda)]

Fixed upstream, may be a candidate for SRU if more reports comes in.

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

This should be fixed in Ubuntu 10.04 now. Thanks for reporting.