transmission-gtk crashed with SIGSEGV in tr_ntop()

Bug #740614 reported by CaptainMark
100
This bug affects 15 people
Affects Status Importance Assigned to Milestone
transmission (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: transmission

transmission unexpected crash

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: transmission-gtk 2.13-0ubuntu7
ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Wed Mar 23 00:20:52 2011
ExecutablePath: /usr/bin/transmission-gtk
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcCmdline: transmission-gtk /tmp/kubuntu-10.10-desktop-amd64.iso.torrent
ProcEnviron:
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x447bd0 <tr_ntop>: mov (%rdi),%ecx
 PC (0x00447bd0) ok
 source "(%rdi)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
 tr_ntop ()
 tr_sessionGetPublicAddress ()
 ?? ()
 ?? ()
 ?? () from /usr/lib/nvidia-current/libGL.so.1
Title: transmission-gtk crashed with SIGSEGV in tr_ntop()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

Revision history for this message
CaptainMark (imark-skinner) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 tr_ntop (src=0x4, dst=0x6ad520 "129.79.43.175", size=46) at net.c:167
 tr_sessionGetPublicAddress (session=<value optimized out>, tr_af_type=<value optimized out>, is_default_value=0x7f1fc183cb38 "\377\377\377\377") at session.c:244
 createEasy (vsession=0x9b4ca0) at web.c:170
 tr_webThreadFunc (vsession=0x9b4ca0) at web.c:303
 ThreadFunc (_t=0x9b97b0) at platform.c:110

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
Revision history for this message
Krzysztof Klimonda (kklimonda) wrote :

Thanks, it's one of patches I've applied yesterday - 0113-fix_support_for_ipv6_trackers.patch. I will investigate it further.

visibility: private → public
Changed in transmission (Ubuntu):
assignee: nobody → Krzysztof Klimonda (kklimonda)
status: New → In Progress
Revision history for this message
Gaurav Kumar (gaurav-b-kumar) wrote :

This crash happened to me after closing transmission, after the "sending upload/download information to trackers" message had been up for a few moments.

tags: added: mago
Revision history for this message
Krzysztof Klimonda (kklimonda) wrote :

Attached is a debdiff that fixes the crash. It's low risk patch for the patch, I've backported from upstream two changes - added another check in tr_sessionGetPublicAddress that guards against empty bindinfo and replaced strcmp with tr_strcmp0 which guards against other possible crash - basically checks if both str1 and str2 are not NULL.

Although the crash so far hasn't been affecting many people, and happens only when application is being closed it did already gather few duplicatesso I'd like to request an approval to upload it before Beta1.

Changed in transmission (Ubuntu):
assignee: Krzysztof Klimonda (kklimonda) → nobody
status: In Progress → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package transmission - 2.13-0ubuntu8

---------------
transmission (2.13-0ubuntu8) natty; urgency=low

  * debian/patches/0113-fix_support_for_ipv6_trackers.patch:
    - update patch to fix the crash it has introduced. (LP: #740614)
 -- Krzysztof Klimonda <email address hidden> Thu, 31 Mar 2011 17:34:58 +0200

Changed in transmission (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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