https://bugs.kde.org/show_bug.cgi?id=512448
--- Comment #6 from Brent Spillner <[email protected]> --- (In reply to TraceyC from comment #3) > Thanks for the crash report. As the message at the top of the summary says, > if something crashed, we need a backtrace of it so we can figure out what's > going on. Can you please attach a backtrace of the crash using the > coredumpctl command-line program, as detailed in > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl ? > > Thanks. plasmashell crashed again today, but I just realized that these particular crashes will /never/ generate a core because it shuts itself down and exits "normally" from the OS perspective, albeit with a non-zero status code, i.e. it's invoking exit(255) instead of raising an uncaught signal. Today's crash was again while the monitors were waking up from sleep, and with a very similiar stderr trace to all of the previous instances (attached). Of note, in case it wasn't clear from my earlier reporting, this is not a deterministic failure; the monitors wake successfully dozens of times between every pair of crashes, and as far as I can recall I've never had two crashes within 24-48 hours of each other (so there may be some resource that's being gradually exhausted). Anyway, I've restarted it, again under GDB, with a breakpoint on exit() this time, and I'll gcore when it quits on me again, but I'm skeptical that will add much value in troubleshooting a fault of this nature in a multithreaded program. -- You are receiving this mail because: You are watching all bug changes.
