Open FichteFoll opened 2 years ago
Does it happen all the time? Or any steps to reproduce? It happened to me once today when the Image worker was retrieving an anime, so it might have to do with the worker threads in the Qt UI.
Does it happen all the time?
Sometimes it does not reproduce, but most of the time it does. I tried closing via ctrl+q, the main menu, and the tray. I also tried browsing my list a bit before closing and doing nothing for a while, but I can't seem to figure out when it does not segfault.
As of 0.8.4.r199.ge132db0-1 it segfaults if you press ctrl-c in the terminal window (assumed that you opened it this way), and then try to close it with the regular window control buttons.
Trackma-qt v0.8.4
Showing debug information.
Engine: Trackma v0.8.4 - using account alsoGAMER(anilist).
Engine: Reading config files...
Data: Initializing...
[D] Data: Reading userconfig...
libanilist: Initializing...
Data: Using libanilist (anime)
[D] Data: Locking database...
[D] Data: Reading metadata...
[D] Data: Reading queue...
[D] Data: Reading info DB...
[D] Data: No items in queue.
libanilist: Downloading list...
[D] Data: Saving userconfig...
[D] Data: Saving cache...
[D] Data: Saving metadata...
Engine: Parsing redirection file...
Engine: Scanning local library...
[D] Engine: Scanning for Watching
[D] Engine: Scanning for Rewatching
[D] Engine: Scanning for Paused
[D] Engine: Scanning for Plan to Watch
[D] Engine: Directory: /home/alsog/Videos
[D] Engine: Time: 0.00087738037109375
Ready.
^C
File "/usr/lib/python3.10/site-packages/trackma/ui/qt/models.py", line 143, in rowCount
def rowCount(self, parent):
KeyboardInterrupt
zsh: IOT instruction (core dumped) trackma-qt -d
I did indeed open it via the terminal (python -m trackma.ui.qt -d
), but I did not use ctrl+c to close (or at least not generally). The segfault happens for me even when trying to close the window normally using the methods I described.
The segfault happens for me even when trying to close the window normally using the methods I described.
Doesn't happen to me, unless I ctrl-c.
I just had the random idea that this might have been caused by the mpris tracker (seeing how it is using a gio loop on a separate (daemon) thread), but after changing the tracker to lsof I can still reproduce the segfault.
Whenever I quit the Qt GUI, I get a segmentation fault.
(139 is the exit code)
Here is a core dump: