mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
A consistent crash caused by a regression in Qt 5.12.4 ( QWidgetBackingStore::markDirtyOnScreen ) #8878
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#8878
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 @birdie-github on GitHub (Jul 8, 2019).
For details please check this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1727583
I know nothing about C++/Qt, so I'm curious if you could write a temporary workaround for this Qt regression since Qt developers aren't rushing to fix it.
Thank you!
@thalieht commented on GitHub (Jul 8, 2019):
Looks like a #9996 duplicate or at least related. These crash reports started since Qt 5.11.1 was adopted (qBT 4.1.2)
@birdie-github commented on GitHub (Jul 8, 2019):
#9996 is a completely different crash report.
This one is about a regression in Qt related to window repainting.
https://bugreports.qt.io/browse/QTBUG-76509
https://bugreports.qt.io/browse/QTBUG-76661
https://bugreports.qt.io/browse/QTBUG-76923
@xavier2k6 commented on GitHub (Nov 14, 2019):
Above bugs have been fixed in Qt 5.12.5 & Qt 5.13.1