segmentation fault (core dump) adding magnet link

General support for problems installing or using Deluge
Post Reply
brainchild
New User
New User
Posts: 5
Joined: Sat Dec 18, 2021 5:36 pm

segmentation fault (core dump) adding magnet link

Post by brainchild »

The application crashes when adding certain magnet links.

I have been running as a daemon, controlled remotely.

The crash manifests as a segmentation fault (core dump).

Following is the stack trace from gdb:

Code: Select all

#0  0x00007ffff5a52bd5 in boost::python::objects::polymorphic_id_generator<libtorrent::alert>::execute(void*) ()
   from /usr/lib/python3/dist-packages/libtorrent.cpython-310-x86_64-linux-gnu.so
#1  0x00007ffff546c354 in ?? ()
   from /lib/x86_64-linux-gnu/libboost_python310.so.1.74.0
#2  0x00007ffff5461ff7 in boost::python::objects::find_instance_impl(_object*, boost::python::type_info, bool) ()
   from /lib/x86_64-linux-gnu/libboost_python310.so.1.74.0
#3  0x00007ffff54620a8 in boost::python::converter::get_lvalue_from_python(_object*, boost::python::converter::registration const&) ()
   from /lib/x86_64-linux-gnu/libboost_python310.so.1.74.0
#4  0x00007ffff5a840a8 in ?? ()
   from /usr/lib/python3/dist-packages/libtorrent.cpython-310-x86_64-linux-gnu.so
#5  0x00007ffff5472244 in boost::python::objects::function::call(_object*, _object*) const () from /lib/x86_64-linux-gnu/libboost_python310.so.1.74.0
#6  0x00007ffff547265c in ?? ()
   from /lib/x86_64-linux-gnu/libboost_python310.so.1.74.0
#7  0x00007ffff546f6e3 in boost::python::handle_exception_impl(boost::function0<void>) () from /lib/x86_64-linux-gnu/libboost_python310.so.1.74.0
#8  0x00007ffff546f7d6 in ?? ()
   from /lib/x86_64-linux-gnu/libboost_python310.so.1.74.0
#9  0x00005555556a630b in _PyObject_MakeTpCall ()
#10 0x00005555556bd99b in ?? ()
#11 0x000055555569e25a in _PyEval_EvalFrameDefault ()
#12 0x00005555556bd80e in ?? ()
#13 0x000055555569a8c4 in _PyEval_EvalFrameDefault ()
#14 0x00005555556affbc in _PyFunction_Vectorcall ()
#15 0x00005555556985c9 in _PyEval_EvalFrameDefault ()
#16 0x00005555556affbc in _PyFunction_Vectorcall ()
#17 0x00005555556985c9 in _PyEval_EvalFrameDefault ()
#18 0x00005555556affbc in _PyFunction_Vectorcall ()
#19 0x00005555556985c9 in _PyEval_EvalFrameDefault ()
#20 0x00005555556affbc in _PyFunction_Vectorcall ()
#21 0x00005555556985c9 in _PyEval_EvalFrameDefault ()
#22 0x00005555556affbc in _PyFunction_Vectorcall ()
#23 0x000055555569a8c4 in _PyEval_EvalFrameDefault ()
#24 0x00005555556affbc in _PyFunction_Vectorcall ()
#25 0x00005555556997d9 in _PyEval_EvalFrameDefault ()
#26 0x00005555556affbc in _PyFunction_Vectorcall ()
#27 0x0000555555698483 in _PyEval_EvalFrameDefault ()
#28 0x0000555555694cc6 in ?? ()
#29 0x0000555555789eb6 in PyEval_EvalCode ()
#30 0x00005555557b7318 in ?? ()
#31 0x00005555557b003b in ?? ()
#32 0x00005555557b7065 in ?? ()
#33 0x00005555557b6548 in _PyRun_SimpleFileObject ()
#34 0x00005555557b6243 in _PyRun_AnyFileObject ()
#35 0x00005555557a6b6e in Py_RunMain ()
#36 0x000055555577ce6d in Py_BytesMain ()
#37 0x00007ffff7c74d90 in __libc_start_call_main (
    main=main@entry=0x55555577ce30, argc=argc@entry=7, 
    argv=argv@entry=0x7fffffffdf38)
    at ../sysdeps/nptl/libc_start_call_main.h:58
#38 0x00007ffff7c74e40 in __libc_start_main_impl (main=0x55555577ce30, argc=7, 
    rgv=0x7fffffffdf38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdf28) at ../csu/libc-start.c:392
#39 0x000055555577cd65 in _start ()
Following is the application information:

Code: Select all

$ deluged --version
deluged 2.1.1
libtorrent: 2.0.5.0
Python: 3.10.4
OS: Linux Linux Mint 21 vanessa
Following is the system information:

Code: Select all

System:
  Kernel: 5.15.0-47-generic x86_64 bits: 64 compiler: gcc v: 11.2.0 Desktop: N/A wm: Xpra
    dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy
Machine:
  Type: Microsoft System: QEMU product: Standard PC (i440FX + PIIX, 1996) v: pc-i440fx-2.2
    serial: <superuser required> Chassis: type: 1 v: pc-i440fx-2.2 serial: <superuser required>
  Mobo: N/A model: N/A serial: N/A BIOS: SeaBIOS v: Virtualization-2.5.1-11303-200428-0-gfff70e7
    date: 04/01/2014
CPU:
  Info: quad core model: AMD Ryzen Embedded V1500B bits: 64 type: MCP arch: Zen rev: 0 cache:
    L1: 384 KiB L2: 2 MiB L3: 4 MiB
  Speed (MHz): avg: 2200 min/max: N/A cores: 1: 2200 2: 2200 3: 2200 4: 2200 bogomips: 17599
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: VMware SVGA II Adapter driver: N/A bus-ID: 00:02.0 chip-ID: 15ad:0405
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: vmware
    unloaded: fbdev,modesetting,vesa gpu: N/A display-ID: :1 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: screen res: 1920x1080 size: N/A
  OpenGL: renderer: llvmpipe (LLVM 13.0.1 256 bits) v: 4.5 Mesa 22.0.5 direct render: Yes
Audio:
  Message: No device data found.
  Sound Server-1: PulseAudio v: 15.99.1 running: yes
  Sound Server-2: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel 82371AB/EB/MB PIIX4 ACPI vendor: Red Hat Qemu virtual machine
    type: network bridge driver: piix4_smbus v: N/A port: N/A bus-ID: 00:01.3 chip-ID: 8086:7113
  Device-2: Red Hat Virtio network driver: virtio-pci v: 1 port: c0a0 bus-ID: 00:03.0
    chip-ID: 1af4:1000
  IF: ens3 state: up speed: -1 duplex: unknown mac: <filter>
  IF-ID-1: br-ff891b4f809b state: down mac: <filter>
  IF-ID-2: docker0 state: down mac: <filter>
Drives:
  Local Storage: total: 888 GiB used: 324.92 GiB (36.6%)
  ID-1: /dev/sda model: Storage size: 128 GiB serial: N/A
  ID-2: /dev/sdb model: Storage size: 10 GiB serial: N/A
  ID-3: /dev/sdc model: Storage size: 250 GiB serial: N/A
  ID-4: /dev/sdd model: Storage size: 250 GiB serial: N/A
  ID-5: /dev/sde model: iSCSI Storage size: 250 GiB serial: N/A
Partition:
  ID-1: / size: 128 GiB used: 86.88 GiB (67.9%) fs: btrfs dev: /dev/sda1
  ID-2: /home size: 128 GiB used: 86.88 GiB (67.9%) fs: btrfs dev: /dev/sda1
Swap:
  ID-1: swap-1 type: partition size: 10 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb
USB:
  Hub-1: 1-0:1 info: Full speed or root hub ports: 2 rev: 1.1 speed: 12 Mb/s chip-ID: 1d6b:0001
  Device-1: 1-1:2 info: Adomax QEMU USB Tablet type: HID driver: hid-generic,usbhid rev: 2.0
    speed: 12 Mb/s chip-ID: 0627:0001
  Hub-2: 2-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002
  Hub-3: 3-0:1 info: Super-speed hub ports: 4 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
Sensors:
  Message: No sensor data found. Is lm-sensors configured?
Repos:
  Packages: apt: 2819
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/deluge-team-stable-jammy.list
    1: deb http: //ppa.launchpad.net/deluge-team/stable/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/flacon-ppa-focal.list
    1: deb http: //ppa.launchpad.net/flacon/ppa/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com vanessa main upstream import backport
    2: deb http: //archive.ubuntu.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //archive.ubuntu.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //archive.ubuntu.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/papirus-papirus-focal.list
    1: deb http: //ppa.launchpad.net/papirus/papirus/ubuntu jammy main
  No active apt repos in: /etc/apt/sources.list.d/wsdd-focal.list
  Active apt repos in: /etc/apt/sources.list.d/xpra-focal.list
    1: deb [arch=amd64,arm64 signed-by=/usr/share/keyrings/xpra-2022.gpg] https: //xpra.org/ jammy main
Info:
  Processes: 263 Uptime: 4h 0m Memory: 7.76 GiB used: 1.25 GiB (16.0%) Init: systemd v: 249
  runlevel: 5 Compilers: gcc: 11.2.0 alt: 11/9 Client: Unknown python3.10 client inxi: 3.3.13
How might I attempt to resolve this problem?
Top
mhertz
Moderator
Moderator
Posts: 2331
Joined: Wed Jan 22, 2014 5:05 am
Location: Denmark

Re: segmentation fault (core dump) adding magnet link

Post by mhertz »

Could you please obtain deluge debug-logs please of the issue thanks.

Code: Select all

deluged -L debug -l deluged.log
(If you have deluged running from systemd and 'deluge' user, then easiest is stop deluged service and rerun temporarilly manually e.g. 'sudo -u deluge deluged -L debug -l deluged.log' or alike.)

Possibly also same for deluge-web, but seems daemon related.

Thanks.

Edit: Hmm, if segmentation fault then not sure will help, and more your traces helpfull, though i'm not good enough to interpret unfortunetly, sorry, hopefully others can help you better then. Apologies.
Top
brainchild
New User
New User
Posts: 5
Joined: Sat Dec 18, 2021 5:36 pm

Re: segmentation fault (core dump) adding magnet link

Post by brainchild »

I had run with debug output, but I have not saved it, because it revealed no relevant information.
Top
Post Reply

Return to “Support”