transmission crashed with SIGSEGV in tr_sessionLock()

[Jānis Kangarooo]

Binary package hint: transmission

somehow crashed-closed

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: transmission-gtk 2.04-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-9.14-generic 2.6.35-rc5
Uname: Linux 2.6.35-9-generic i686
Architecture: i386
Date: Thu Aug 19 12:59:24 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/transmission
InstallationMedia: Xubuntu 10.10 "Maverick Meerkat" - Alpha i386 (20100701)
ProcCmdline: transmission
ProcCwd: /home/kng
ProcEnviron:
 LANG=lv_LV.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8093f59 <tr_sessionLock+9>: mov 0xd8(%eax),%eax
 PC (0x08093f59) ok
 source "0xd8(%eax)" (0x0c81c400) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
 tr_sessionLock ()
 ?? ()
 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 tr_sessionLock()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 tr_sessionLock (session=0xc81c328) at session.c:953
 canReadWrapper (io=0xb0ad0018) at peer-io.c:133
 event_base_loop (base=0x8820078, flags=0) at event.c:385
 event_loop (flags=0) at event.c:461
 event_dispatch () at event.c:399

[Charles Kerr (charlesk)]

Hi Kangaroo,

When you say crashed-closed do you mean it crashed while the application was shutting down? If not, do you remember what you were doing when it crashed?

[Charlie Kravetz (cjkgeek)]

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!

[Charles Kerr (charlesk)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Chascon (chascone)]

I've had the issue when closing.

[Rolf Leggewie (r0lf)]

does this ever occur in trusty or later?

[Rolf Leggewie (r0lf)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!