Crash due to glib

[Olorin]

Nearly everyday, and sometimes several times a day, I have this crash :

GLib-ERROR **: Cannot create pipe main loop wake-up: Trop de fichiers ouverts

aborting...

*************************************************************
Catching SIGABRT, please report a bug at http://bug.qbittorrent.org
and provide the following backtrace:
qBittorrent version: v2.4.10
stack trace:
  [0xb77ea400]
  [0xb77ea424]
  /lib/i686/cmov/libc.so.6 : gsignal()+0x51 [0xb61df751]
  /lib/i686/cmov/libc.so.6 : abort()+0x182 [0xb61e2b82]
  /lib/libglib-2.0.so.0 : ()+0x45c0e [0xb600ec0e]
  /lib/libglib-2.0.so.0 : g_log()+0x26 [0xb600ec36]
  /lib/libglib-2.0.so.0 : ()+0x3befd [0xb6004efd]
  /lib/libglib-2.0.so.0 : g_main_context_new()+0x94 [0xb6004f94]
  /usr/lib/libQtCore.so.4 : QEventDispatcherGlibPrivate::QEventDispatcherGlibPrivate(_GMainContext*)+0x202 [0xb65cd822]
  /usr/lib/libQtCore.so.4 : QEventDispatcherGlib::QEventDispatcherGlib(QObject*)+0x3b [0xb65cda4b]
  /usr/lib/libQtCore.so.4 : ()+0x6fe04 [0xb64a4e04]
  /usr/lib/libQtCore.so.4 : ()+0x6ff95 [0xb64a4f95]
  /lib/i686/cmov/libpthread.so.0 : ()+0x5955 [0xb734b955]
  /lib/i686/cmov/libc.so.6 : clone()+0x5e [0xb6280e7e]

Only one or two download files at a time (so I don't understand the "to many files open" message)

Debian SID
libglib 2.24.2-1
libQtCore 4:4.6.3-4
libc6 2.11.2-7
libtorrent-rasterbar 0.14.10-2+b1

[Christophe Dumez (hydr0g3n)]

I really don't think this is a bug. This is more likely to be a configuration problem in qBittorrent or in your system.

Please try reducing the maximum number of connections in qBittorrent preferences.

[Olorin (bilbo1777)]

Yes, I thought about it after filling the report, I ha raised the max number of connections to 1000 to test, and forgotten to reduced it back to 500. I did it today and I had no crash.

But it could be good to have a proper error message in that case (the reason is not obvious when you have a crash without any message) or, better, to detect the problem and limit automatically the connections if possible (but that might be tricky)

[Christophe Dumez (hydr0g3n)]

The message in unhelpful because it comes from the system, not qBittorrent. qBittorrent is being killed by the system because it uses too many files (or sockets in this case). qBittorrent can be killed by the system for any reason and I really don't know how I can detect that.

Detecting the number of open sockets, the limit and adjusting automatically would of course be nice. I will look into it but this seems difficult.