https://bugs.kde.org/show_bug.cgi?id=503887
--- Comment #2 from Sebastian Kenn <s.k...@gmx.de> --- (In reply to Nate Graham from comment #1) > Thanks, but I'm afraid the file you attached has no backtrace of the crash > in it. We need this to debug it. Can you follow the instructions at > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl > and get one? > > Thanks! Remember: "I'm also having problems with gdb since some month, which regularly floods RAM after crashes. This happens here too, but it's probably an unrelated bug." Gdb produces some GB in RAM until the system collapses. I solve this problem by killing gdb. No gdb - no backtrace, sorry. Maybe I need to solve this problem first. If you have any ideas, let me know. -- You are receiving this mail because: You are watching all bug changes.
