transmission-gtk crashed with SIGSEGV in tr_sessionLock()

[Kirill I.]

#

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: transmission-gtk 2.84-3ubuntu3.1
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CurrentDesktop: LXDE
Date: Sat Apr 28 03:38:48 2018
ExecutablePath: /usr/bin/transmission-gtk
InstallationDate: Installed on 2012-05-25 (2163 days ago)
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
ProcCmdline: transmission-gtk magnet:?xt=urn:btih:DD48177A84474DD869212D9E8934CC894ECB3A4B&dn=heroes+of+might+and+magic+iii+2+0+0+16+patch+2+0+1+17+gog&tr=udp%3A%2F%2Ftracker.istole.it%3A80%2Fannounce&tr=udp%3A%2F%2Fglotorrents.pw%3A6969%2Fannounce
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x55a50e7fc320 <tr_sessionLock>: mov 0x1b8(%rdi),%rdi
 PC (0x55a50e7fc320) ok
 source "0x1b8(%rdi)" (0x000001b7) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
 tr_sessionLock ()
 tr_torrentRecheckCompleteness ()
 ?? ()
 ?? ()
 event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5
Title: transmission-gtk crashed with SIGSEGV in tr_sessionLock()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-tor dialout dip disk libvirtd lp lpadmin plugdev sambashare sudo vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1726166, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.