Ubuntu
transmission package

transmission-gtk crashed with SIGSEGV in __GI___pthread_mutex_lock()

Bug #1199082 reported by Lockal
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
transmission (Ubuntu)
Confirmed
Medium
Weiller

Bug Description

Transmission crashed after rightclicking while navigating the torrent list in main window.

Not sure how to reproduce, but the stack trace may indicate in which circumstances it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: transmission-gtk 2.80-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
Date: Tue Jul 9 01:58:08 2013
ExecutablePath: /usr/bin/transmission-gtk
InstallationDate: Installed on 2012-02-05 (519 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
MarkForUpload: True
ProcCmdline: transmission-gtk /tmp/t1671.torrent
SegvAnalysis:
 Segfault happened at: 0x7f97cc6a0f94 <__GI___pthread_mutex_lock+4>: mov 0x10(%rdi),%esi
 PC (0x7f97cc6a0f94) ok
 source "0x10(%rdi)" (0x0000001c) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
 __GI___pthread_mutex_lock (mutex=0x7f97a8573dc0) at pthread_mutex_lock.c:50
 tr_lockLock ()
 tr_torrentRecheckCompleteness ()
 ?? ()
 ?? ()
Title: transmission-gtk crashed with SIGSEGV in __GI___pthread_mutex_lock()
UpgradeStatus: Upgraded to saucy on 2013-05-19 (50 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

See original description
Revision history for this message
Lockal (lockal) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __GI___pthread_mutex_lock (mutex=0x7f97a8573dc0) at pthread_mutex_lock.c:50
 tr_lockLock (l=0x4) at platform.c:234
 tr_sessionLock (session=<optimized out>) at session.c:1072
 tr_torrentLock (tor=0x7f97d090eb00) at torrent.h:314
 tr_torrentRecheckCompleteness (tor=tor@entry=0x7f97d090eb00) at torrent.c:2126

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in transmission (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Lockal (lockal)
information type: Private → Public
Revision history for this message
Charles Kerr (charlesk) wrote :

Hi Lockal, from the stacktrace it looks like a null pointer's being dereferenced in tr_sessionLock()'s call to "tr_lockLock (session->lock);" ... however, session->lock is initialized on startup and then never changed until shutdown. So maybe the crash reporter tool got confused with which report it sent with your summary, or maybe there's some memory corruption going on that NULLed that pointer out.

Lockal, are you able to reproduce this bug?

Charles Kerr (charlesk)
Changed in transmission (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for transmission (Ubuntu) because there has been no activity for 60 days.]

Changed in transmission (Ubuntu):
status: Incomplete → Expired
Lockal (lockal)
description: updated
Revision history for this message
Weiller (weillerronfini) wrote :

Confirmed for this bug affects me too.

Changed in transmission (Ubuntu):
assignee: nobody → Weiller (weillerronfini)
status: Expired → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.