transmission crashed with SIGSEGV in g_main_context_dispatch()

Bug #322614 reported by nils
20
Affects Status Importance Assigned to Milestone
Transmission
Invalid
Unknown
transmission (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: transmission

Ubuntu jaunty (development branch)
Release: 9.04

transmission:
Kandidat: 1.42-0ubuntu1
Versions-Tabelle:
1.42-0ubuntu1 0

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/transmission
Package: transmission-gtk 1.42-0ubuntu1
ProcCmdline: transmission
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: transmission
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/libglib-2.0.so.0
 g_main_loop_run () from /usr/lib/libglib-2.0.so.0
Title: transmission crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.27-8-eeepc i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
nils (nils-lienshoeft) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:g_timeout_dispatch (source=0xb2f9dc78, callback=0,
IA__g_main_context_dispatch (context=0x98d4920)
g_main_context_iterate (context=0x98d4920, block=1,
IA__g_main_loop_run (loop=0x9c62650)
IA__gtk_main ()

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
Hew (hew) wrote :

Thanks for your report. Does the problem still exist with Ubuntu Jaunty and transmission 1.51-0ubuntu1?

Changed in transmission:
status: New → Incomplete
Revision history for this message
Nicholas Wilson (wilsonnck) wrote :

I experienced this bug on Jaunty Alpha-5 with the following packages installed:

transmission-common 1.51-0ubuntu1
transmission-gtk 1.51-0ubuntu1

You can see my report in the duplicates.

Revision history for this message
Hew (hew) wrote :

Thanks, reported upstream at http://trac.transmissionbt.com/ticket/1880

Changed in transmission:
status: Incomplete → Triaged
Changed in transmission:
status: Unknown → New
Revision history for this message
Charles Kerr (charlesk) wrote :

Nicholas: the trace in that duplicate ticket is only three lines long, and doesn't even include any Transmission code. I'm happy to look into this, but is there any more information for me to go on in the 1.51 crash? This 1.42 ticket has a retraced stacktrace... is there nothing like that for the 1.51 occurance?

Revision history for this message
Hew (hew) wrote :

The duplicate had its attachments removed by the silly retracer. I did some quick googling and managed to save them, but as they haven't been retraced they are missing debug symbols. I have attached the ThreadStacktrace anyway, in case it is of some assistance.

Nicholas, could you please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report? This will greatly help us in tracking down your problem. Thanks in advance.

Revision history for this message
Nicholas Wilson (wilsonnck) wrote :
Changed in transmission:
status: New → Invalid
Revision history for this message
Hew (hew) wrote :

Have you been able to reproduce the crash again?

Changed in transmission (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Peter B P (peterbp) wrote : Re: [Bug 322614] Re: transmission crashed with SIGSEGV in g_main_context_dispatch()

On Sun, 2009-03-29 at 04:30 +0000, Hew McLachlan wrote:
> Have you been able to reproduce the crash again?
>
> ** Changed in: transmission (Ubuntu)
> Status: Triaged => Incomplete
>

Dear Hew,

thanks for mailing me. I think so, but to be honest, I'm not sure. Long
story short, I'm new to Launchpad and the bug reporting business, and I
have in fact had a handful of Transmission crashes over the last week,
but whenever Apport pops up, I can see it compiles crash reports that
are, MegaByte-wise, well into the double digits (smallest 21 MB, biggest
91 MB!), and whever I send them off, the Launchpad page that usually
results from sending a crash report gives me a timeout error, without
showing me the description of the crash I submitted.

Regarding the crashes, they seem semi-repriducible, and sometimes happen
when I open the "properties" of an active torrent, click around the tabs
(typically peers and tracker), and afterwards choose to close the
properties window. Te result is full CPU use for about 5 seconds, and
then a crash.

If my reports have been choking your bug submission system, I apologize,
but I don't know how to shorten down the amount of data that I send off
to you.

a good weekend to you,

--

regards,
Peter B. Perlsø, +45 2685 5909

Revision history for this message
Peter B P (peterbp) wrote :

Ah, sorry for the above, but on topic: I can still provoke the crashes from time to time (Jaunty beta, Transmission 1.51), MO is the same - the Transmission run overnight with a handful of open torrents, open the properties for any torrent a couple of times, poke around the various tabs, click CLose, and it hangs for a minute, then quits.

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

Looking at the retrace again, I figured it out.

This is a similar permutation of #359319 and has the same fix as that commit. The properties dialog's periodic update timer had a problem where the timer might not have deleted when the properties dialog was closed.

The giveaway is the call to periodic_refresh().

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

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