transmission-gtk crashed with SIGSEGV in fileset_close_torrent()

[damaex]

no idea what happened. i started a movie via mplayer from the command line and compiz crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: transmission-gtk 2.50-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9
Uname: Linux 3.2.0-18-generic x86_64
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
Date: Tue Mar 13 20:19:59 2012
ExecutablePath: /usr/bin/transmission-gtk
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: transmission-gtk magnet:?xt=urn:btih:E2C3127D640A2B2830F60C0FEB82B337509A444D&dn=Justified\ S01E09\ HDTV\ XviD-LOL.avi&tr=http://tracker.openbittorrent.com:80/announce&tr=http://tracker.publicbt.com:80/announce&tr=http://tracker.istole.it:80/announce&tr=http://tracker.hexagon.cc:2710/announce&tr=udp://tracker.1337x.org:80/announce
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x44569b <tr_fdTorrentClose+43>: cmp 0x8(%rbp),%ebx
 PC (0x0044569b) ok
 source "0x8(%rbp)" (0x00001439) not located in a known VMA region (needed readable region)!
 destination "%ebx" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: transmission
StacktraceTop:
 tr_fdTorrentClose ()
 tr_torrentRecheckCompleteness ()
 ?? ()
 ?? ()
 event_base_loop () from /usr/lib/libevent-2.0.so.5
Title: transmission-gtk crashed with SIGSEGV in tr_fdTorrentClose()
UpgradeStatus: Upgraded to precise on 2012-03-02 (12 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 fileset_close_torrent (torrent_id=-1, set=0x17941f8) at fdlimit.c:461
 tr_fdTorrentClose (session=<optimized out>, torrent_id=-1) at fdlimit.c:623
 tr_torrentRecheckCompleteness (tor=0x14cf000) at torrent.c:2046
 torrentRecheckDoneImpl (vtor=0x14cf000) at torrent.c:1698
 readFromPipe (fd=9, eventType=<optimized out>, veh=0x1131910) at trevent.c:192

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.