search

qbittorrent / qBittorrent

qBittorrent BitTorrent client
https://www.qbittorrent.org
Other
26.83k stars 3.87k forks source link

SIGSEV crash #597

Closed XXLRay closed 11 years ago

XXLRay commented 11 years ago

After upgrading qbittorrent to version 3.0.9 from the ppa on Ubuntu 12.04 it still crashes with the following error message after some minutes:

Catching SIGSEGV, please report a bug at http://bug.qbittorrent.org and provide the following backtrace: qBittorrent version: v3.0.9 stack trace: /lib/x86_64-linux-gnu/libc.so.6 : ()+0x364a0 [0x7fa6a0bae4a0] /lib/x86_64-linux-gnu/libcrypto.so.1.0.0 : RC4()+0x3bd [0x7fa6a3a4903d] Segmentation fault (core dumped)

As far as I can see this is the same as with version 2.9.7 which comes with Ubuntu 12.04.

dcotruta commented 11 years ago

I second this, on Fedora 17, exactly the same core dump. This is now so bad I have to switch clients. I would normally offer to fix this myself, but I don't have the time at the moment.

dcotruta commented 11 years ago

I should have mentioned I am going to try running with encryption disabled and report back.

sledgehammer999 commented 11 years ago

From the core dump the problem seems to be somewhere inside openssl(libcrypto). As far as I know the most usage of openssl is done by libtorrent. So maybe, it is a miscompilation or a bug inside libtorrent/openssl code. If I remember correctly, the only place where qbittorrent uses openssl directly(via qt) is in the webui when you have enabled ssl authentication.

@XXLRay what version of libtorrent and openssl is used?

XXLRay commented 11 years ago

The program is more stable if I close it cleanly directly after I started it from a crash.

$ openssl version OpenSSL 1.0.1 14 Mar 2012

But how do I find out the libtorrent version?

sledgehammer999 commented 11 years ago

From your package manager(eg synaptic). Also from qbittorrent: help->about->libraries (the two versions should match)

XXLRay commented 11 years ago

Which of these is the one I should check for its version number?:

$ sudo apt-cache search libtorrent

... libtorrent-dev - C++ BitTorrent library by Rakshasa (development files) libtorrent-rasterbar-dbg - Debug symbols for libtorrent-rasterbar libtorrent-rasterbar-dev - Development files for libtorrent-rasterbar libtorrent-rasterbar-doc - Documentation for libtorrent-rasterbar libtorrent-rasterbar6 - C++ bittorrent library by Rasterbar Software libtorrent-ruby - BitTorrent library in Ruby libtorrent-ruby1.8 - BitTorrent library in Ruby libtorrent14 - C++ BitTorrent library by Rakshasa ...

Help -> about -> Libraries shows:

Qt: 4.8.1 Libtorrent: 0.15.10.0 Boost: 1.46.1

Tg8igPGjh3 commented 11 years ago

@dcotruta anything? did it work?

Goutte commented 11 years ago

Just to bump this issue :

qBittorrent version: v2.9.8
stack trace:
  /lib/x86_64-linux-gnu/libc.so.6 : ()+0x324f0  [0x7f932c2874f0]
  /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 : RC4()+0x1de  [0x7f932ee615de]
Erreur de segmentation

I'm on Debian Wheezy, using the default repositories, and OpenSSL 1.0.1e 11 Feb 2013.

I use magnets, but no WebUI.

This is really frightening, due to the random nature of the crash, and that such crashes may be a symptom of an open door for arbitrary code execution.

Gloomy theories won't get me anywhere ; can I start qbitorrent in verbose mode to watch connections and get us more data to munch on ?

Meanwhile, this is a show-stopper.

Good hunting !

PhilosopherRex commented 11 years ago

I've the exact same setup running for three weeks non-stop without any
problem -same as you, I use magnets, but no web-gui. Steps to reproduce?
How long does it run before crashing?

On Fri, 05 Jul 2013 15:04:01 +1000, Antoine Goutenoir
notifications@github.com wrote:

Just to bump this issue :

qBittorrent version: v2.9.8
stack trace:
  /lib/x86_64-linux-gnu/libc.so.6 : ()+0x324f0  [0x7f932c2874f0]
  /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 : RC4()+0x1de   
[0x7f932ee615de]
Erreur de segmentation

I'm on Debian Wheezy, using the default repositories, and OpenSSL 1.0.1e
11 Feb 2013.

I use magnets, but no WebUI.

This is really frightening, due to the random nature of the crash, and
that such crashes may be a symptom of an open door for arbitrary code
execution.

Gloomy theories won't get me anywhere ; can I start qbitorrent in
verbose mode to watch connections and get us more data to munch on ?

Meanwhile, this is a show-stopper.

Good hunting !

Reply to this email directly or view it on GitHub: https://github.com/qbittorrent/qBittorrent/issues/597#issuecomment-20501452

sledgehammer999 commented 11 years ago

As bug #750

  1. Install -dbg package of openssl, libtorrent, qbittorrent.
  2. Open a terminal and type 'gdb qbittorrent'
  3. Then type 'run'
  4. When it crashes type 'bt' and then 'thread apply all bt'

Copy all output from the begining (gdb qbittorrent).

sledgehammer999 commented 11 years ago

See bug #750

This clearly appears that it isn't a qBittorrent bug. I am closing this.

I have reported it to the Debian Bugtracker. You can track the bug here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717933

Other distros' users please reported it to your distro's bug trakcer too.