transmission-gtk crashed with SIGSEGV in curl_multi_cleanup()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
transmission (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Happened when I shut it down.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: transmission-gtk 2.77-0ubuntu1
ProcVersionSign
Uname: Linux 3.8.0-14-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Thu Mar 28 10:55:21 2013
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2012-09-29 (179 days ago)
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
ProcCmdline: transmission-gtk /home/username/
SegvAnalysis:
Segfault happened at: 0x7fafe893e5a0 <curl_multi_
PC (0x7fafe893e5a0) ok
source "%rax" ok
destination "(%rdi)" (0x00000000) not located in a known VMA region (needed writable region)!
Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
curl_multi_cleanup () from /usr/lib/
?? ()
?? ()
start_thread () from /lib/x86_
clone () from /lib/x86_
Title: transmission-gtk crashed with SIGSEGV in curl_multi_
UpgradeStatus: Upgraded to raring on 2013-03-03 (24 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1124508, 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.