transmission crashed with SIGSEGV

Bug #204677 reported by Cristian Aravena Romero
10
Affects Status Importance Assigned to Milestone
Transmission
Invalid
Unknown
transmission (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: transmission

Close transmission and crash

ProblemType: Crash
Architecture: i386
Date: Mon Mar 17 08:35:23 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/transmission
Package: transmission-gtk 1.06-0ubuntu1
PackageArchitecture: i386
ProcCmdline: transmission
ProcCwd: /home/caravena
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: transmission
StacktraceTop:
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: transmission crashed with SIGSEGV
Uname: Linux 2.6.25-rc4 i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt sambashare scanner video

Tags: apport-crash
Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_closure_invoke (closure=0x80f92b0, return_value=0x0, n_param_values=1,
signal_emit_unlocked_R (node=0x816ea70, detail=0, instance=0x8735070,
IA__g_signal_emit_by_name (instance=0x8735070,
IA__g_signal_emitv (instance_and_params=0x8735070, signal_id=109, detail=0,
handle_keys_changed (data=0xb7ec7d9c)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in transmission:
importance: Undecided → Medium
Revision history for this message
Charles Kerr (charlesk) wrote :

Could you please attach your file "/home/caravena/.transmission/gtk/prefs.ini" ?

Revision history for this message
Charles Kerr (charlesk) wrote :

Actually, let me change that request... it appears to me that these backtraces are suspect, because (1) they are showing very different crash locations, and (2) ThreadStacktrace.txt (retrace) says that we're crashing in GMemChunk calls inside of GKeyFile in glib 2.16.1, but I've been looking at the source and GKeyFile doesn't call GMemChunk.

So, the first thing to do IMO is to make sure that your libraries are in order. If you're positive that isn't the case, then run Transmission inside of valgrind to figure out where the memory corruption is coming from. If you download Transmission from svn, there's a bash script in the gtk/ directory for running Transmission under valgrind's microscope.

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Changed in transmission:
status: Unknown → Invalid
Revision history for this message
Charles Kerr (charlesk) wrote :

Christian: see my second message on 2008-03-23

Revision history for this message
Charles Kerr (charlesk) wrote :

    *

As I discussed on Launchpad, I think this backtrace is suspect because it says that we're crashing inside GMemChunk, called by GKeyFile, in glib 2.16.1. However I've just been looking at glib 2.16.1's source and GMemChunk isn't used by GKeyFile (in fact, since it's deprecated it's not called by any other glib or Transmission code).

So my first thought is that this is some kind of ABI library shear problem, and I suggest you upgrade Transmission and/or build from source to test that way. If a copy of Transmission built from source crashes, I'm very much interested in that.

Also, it would be good if you could provide a valgrind log generated by the bash script from transmission/gtk/my-valgrind.sh in svn.

Marking as invalid because there's nothing usable in the report to date... but obviously if the problem persists in a fresh build I'm very interested in hearing about it.

Changed in transmission:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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