Ticket #844 (closed bug: fixed)

Opened 4 years ago

Last modified 3 years ago

deluged segmentation fault

Reported by: sasha.sirotkin@… Owned by: andar
Priority: major Milestone:
Component: core Version: 1.1.4
Keywords: Cc:

Description

deluged started segfaulting recently. I did not do anything unusual that might have triggered this, apart from starting to download many (a few dozens) torrents.

I have a core dump but I have no idea what whether it is useful with python.

log file does not have any suspicious messages.

Don't know whether it's related or not, but it also segfaults when I try to remove the attached torrent.

Attachments

Cidade de Deus [mininova].torrent (110.5 KB) - added by sasha.sirotkin@… 4 years ago.
torrent
trace.txt.gz (1.8 KB) - added by sasha.sirotkin@… 4 years ago.
gdb trace

Change History

Changed 4 years ago by sasha.sirotkin@…

torrent

Changed 4 years ago by andar

Please get a back trace.

Changed 4 years ago by sasha.sirotkin@…

Please see the trace file.

I've noticed that it happens when there are many torrents being downloaded. It appears that some file somehow gets corrupted and after that every time deluge tries to process that corrupt file it crashes. The reason I think this is the case is that at first it crashes during normal operation and after that it crashes every time on startup while checking the downloads.

Changed 4 years ago by sasha.sirotkin@…

gdb trace

Changed 4 years ago by sasha.sirotkin@…

Upgraded to 1.1.6, no change, still crashing

Changed 4 years ago by andar

What version of libtorrent are you using?

Changed 4 years ago by sasha.sirotkin@…

The one that comes with standard FC10 rpm (deluge-1.1.6-1.fc10.i386), no idea what it is.

Changed 4 years ago by andar

Try turning DHT and Peer Exchange off..

Changed 4 years ago by sasha.sirotkin@…

Same shit, still crashes. I've noticed that it usually happens when I add a few new torrents simultaneously.

Changed 3 years ago by andar

  • status changed from new to closed
  • resolution set to fixed

I believe this is fixed in the latest.

Note: See TracTickets for help on using tickets.