[Discover] [Bug 506919] Discover crashed in AbstractBackendUpdater::progressingChanged() when I left it to download an offline update
https://bugs.kde.org/show_bug.cgi?id=506919 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #16 from Bug Janitor Service --- 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 506919] Discover crashed in AbstractBackendUpdater::progressingChanged() when I left it to download an offline update
https://bugs.kde.org/show_bug.cgi?id=506919 --- Comment #15 from Bug Janitor Service --- 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 506919] Discover crashed in AbstractBackendUpdater::progressingChanged() when I left it to download an offline update
https://bugs.kde.org/show_bug.cgi?id=506919 --- Comment #14 from Roke Julian Lockhart Beedell <[email protected]> --- (In reply to Harald Sitter from comment #13) > Can someone who can reproduce this problem maybe run discover through > valgrind? Being the reporter, if a consistent reproduction method is ascertained, I can, immediately – unless https://github.com/KDAB/hotspot/issues/728#issuecomment-3164238641 recurs, although it should be unique. Otherwise, I suppose that I could just run Discover through Valgrind 24/7, waiting for a segmentation fault. However, I've yet to see it recur this month, so I don't know how feasible that is. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 506919] Discover crashed in AbstractBackendUpdater::progressingChanged() when I left it to download an offline update
https://bugs.kde.org/show_bug.cgi?id=506919 Harald Sitter changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #13 from Harald Sitter --- Lifetime management is super convoluted here and the theory would be that we are simply tapping into an already deleted object, depending on timings (that we may well only hit on fedora for some reason). We have a deleteLater, a manual delete, a setTransaction which relinquishes control of the UpdateTransaction but also taking control of an outside created transaction (albeit in a strangely different way than when the UpdateTransaction constructs -- why are we even re-managing signal connections?), we also have non-trivial connections to the destroyed signals (huge risk of blowing up on partially destructed object trees which I think we are seeing in at least some of the sentry events with wildly different traces). All that said, since the sentry issue is an amalgam of at least 6 different crashes I've seen so far, I cannot dig for context or find anything. Can someone who can reproduce this problem maybe run discover through valgrind? And maybe also build it with a patch from source so we can add some checks? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 506919] Discover crashed in AbstractBackendUpdater::progressingChanged() when I left it to download an offline update
https://bugs.kde.org/show_bug.cgi?id=506919 Harald Sitter changed: What|Removed |Added CC||[email protected] --- Comment #12 from Harald Sitter --- That sentry issue has had unrelated crashes merged into it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 506919] Discover crashed in AbstractBackendUpdater::progressingChanged() when I left it to download an offline update
https://bugs.kde.org/show_bug.cgi?id=506919 Nate Graham changed: What|Removed |Added Summary|Plasma Discover crashed in |Discover crashed in |AbstractBackendUpdater::pro |AbstractBackendUpdater::pro |gressingChanged() when I|gressingChanged() when I |left it to download an |left it to download an |offline update |offline update -- You are receiving this mail because: You are watching all bug changes.
