| Summary: | drkonqi crashes after click on "Retry" button | ||
|---|---|---|---|
| Product: | [Applications] drkonqi | Reporter: | Patrick Silva <bugseforuns> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | kde, nate, sitter |
| Priority: | HI | ||
| Version First Reported In: | 6.3.90 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | https://invent.kde.org/plasma/drkonqi/-/commit/d59289319474a3be8a588f73a461f6b696e7ef91 | Version Fixed/Implemented In: | |
| Sentry Crash Report: | |||
|
Description
Patrick Silva
2025-05-17 09:14:23 UTC
Guarding is easy, but I can't see a path causing this.
We have:
connect(m_proc, &KProcess::errorOccurred, this, &BacktraceGenerator::slotOnErrorOccurred);
which means the m_proc process is alive, but the member variable is null.
The only option for m_proc to be null when in this path is:
```
void BacktraceGenerator::setBackendFailed()
{
// Shouldn't have been set yet
Q_ASSERT(!m_proc);
m_proc = nullptr;
}
```
that unsets but doesn't delete because of the assumption above.
Every other path does.
*** Bug 504388 has been marked as a duplicate of this bug. *** A possibly relevant merge request was started @ https://invent.kde.org/plasma/drkonqi/-/merge_requests/333 Git commit d59289319474a3be8a588f73a461f6b696e7ef91 by Harald Sitter. Committed on 26/05/2025 at 11:12. Pushed by sitter into branch 'Plasma/6.4'. 🍒backtracegenerator: don't crash when the proc was already deleted (cherry picked from commit 8e2971a992281ffc7dd06c0bc781c6fb0ff9ffaf) Co-authored-by: Harald Sitter sitter@kde.org M +4 -0 src/backtracegenerator.cpp https://invent.kde.org/plasma/drkonqi/-/commit/d59289319474a3be8a588f73a461f6b696e7ef91 |