Summary: | Kicker crash in TaskContainer::popupMenu() | ||
---|---|---|---|
Product: | [Unmaintained] kicker | Reporter: | Emmeran Seehuber <rototor> |
Component: | general | Assignee: | Aaron J. Seigo <aseigo> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | bugs.kde.org, Michael1987 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Crash report |
Description
Emmeran Seehuber
2005-01-31 08:54:38 UTC
and what were you doing, exactly, when the crash happened? without a description of what you were doing it becomes that much harder to solve. thanks. if this is repeatable, can you please recompile kicker with debug symbols so we can see on what exact line this is dieing? popupMenu consists of a fair amount of code. Sorry, but I don't remember exaclty what I was doing. The only thing I remember was that the machine was under load and I wanted to switch to another task. I'll recompile kicker with debug symbols as soon as Beta2 is out. Maybe I can repeat the crash, I just don't know how ... It may make sense to refactor popupMenu() into smaller methods, so that a reason for a crash is more easily located. > I'll recompile kicker with debug symbols as soon as Beta2 is out did you manage to do this? if not, could you do so with the upcoming 3.4rc1 release? thanks > It may make sense to refactor popupMenu() into smaller methods, so that a > reason for a crash is more easily located. the method is not very long, it just has a few different branches in it. *** Bug has been marked as fixed ***. Created attachment 18275 [details]
Crash report
Crash report on shutdown
The crash report shown above was obtained after shutdown with KDE version 3.5.5. It shows a similar behavior as the one posted before. This bug does not seem to be resolved to me. Reopening since I see incoming reports with the same backtrace. *** Bug 136824 has been marked as a duplicate of this bug. *** *** Bug 142476 has been marked as a duplicate of this bug. *** Can someone confirm this bug for a recent KDE version? Please reopen if you do. |