mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
latest git segfault #5465
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#5465
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ERYuyNIrbNKrsc on GitHub (Apr 24, 2017).
Originally assigned to: @glassez on GitHub.
Please provide the following information
qBittorrent version and Operating System:
qBittorrent v3.4.0alpha Kubuntu 17.04
If on linux, libtorrent and Qt version:
libtorrent RC_1_1 Qt 5.7.1
What is the problem:
when updated rss, sometimes happens Segmentation fault
What is the expected behavior:
Steps to reproduce:
Extra info(if any):
@zeule commented on GitHub (Apr 24, 2017):
@glassez?
@glassez commented on GitHub (Apr 24, 2017):
@ERYuyNIrbNKrsc, can you test updated master?
@ERYuyNIrbNKrsc commented on GitHub (Apr 24, 2017):
ok testing, if happens again I'll write here.
@zeule commented on GitHub (Apr 24, 2017):
Thanks!
@ERYuyNIrbNKrsc commented on GitHub (Apr 24, 2017):
updated master
@zeule commented on GitHub (Apr 24, 2017):
Please, paste stacktraces enquoted by ``` (see your edited posts).
@glassez commented on GitHub (Apr 24, 2017):
I'll try to reproduce this crash and fix it again ASAP.
@Chocobo1 commented on GitHub (Apr 24, 2017):
@glassez
coverity scan reported some in rss modules.
@glassez commented on GitHub (Apr 24, 2017):
Fixed in #6686.
But it's not about that.
I can't reproduce it yet...
@glassez commented on GitHub (Apr 24, 2017):
@mgziminsky, can you confirm this issue?
@mgziminsky commented on GitHub (Apr 24, 2017):
I'll test tonight. Based on that stack trace, it looks related to updating a "full" feed.
To test, I would load a feed, with at least 50 articles, then lower that number to maybe 25 and refresh the feed. You should use a feed with frequent updates so that the refresh has some new entries and it doesn't skip everything. Depending on when it reads from the cache file, you might be able to just delete the top few entries from there before refreshing as well.
@zeule commented on GitHub (Apr 24, 2017):
While others trying to reproduce this, @ERYuyNIrbNKrsc, can you rebuild with sanitizer enabled and provide its output when it detects segmentation error, please? Please add the following compiler options:
-fsanitize=address -fsanitize=undefined@ERYuyNIrbNKrsc commented on GitHub (Apr 24, 2017):
possibly related to it.
When this happens, the computer was heavily loaded. (building digiKam)
or is it just my problem ...
@glassez commented on GitHub (Apr 25, 2017):
I've found some bugs in the code, one of them is probably related to this issue. I'll fix it ASAP and let you know.
@glassez commented on GitHub (Apr 25, 2017):
@ERYuyNIrbNKrsc, can you test PR #6686 before I merge it?
UPD: You can do the following:
@ERYuyNIrbNKrsc commented on GitHub (Apr 25, 2017):
ok testing.
@ERYuyNIrbNKrsc commented on GitHub (Apr 25, 2017):
it seems that the problem no longer exists.
@glassez commented on GitHub (Apr 27, 2017):
@ERYuyNIrbNKrsc, fix was merged into master. If this problem no longer exists, please close this issue.