Bug 356741 - konsole crashes after having several sessions of youtube-dl running and the machine came back from standby (suspend to RAM).
Summary: konsole crashes after having several sessions of youtube-dl running and the m...
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 15.08.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: drkonqi
: 381878 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-12-15 16:55 UTC by stakanov.s
Modified: 2020-12-02 22:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description stakanov.s 2015-12-15 16:55:28 UTC
Application: konsole (15.08.0)

Qt Version: 5.5.0
Operating System: Linux 4.1.13-5-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
closing konsole after the jobs where done. Three jobs in different tabs where running when I went away. 
- Unusual behavior I noticed:
One or two of the jobs where signing 100% but not done. When pressing enter they signed done and returned to prompt. 
Closing kontakt then crashed the application.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f7e15407187 in raise () at /lib64/libc.so.6
#7  0x00007f7e15408538 in abort () at /lib64/libc.so.6
#8  0x00007f7e15444804 in  () at /lib64/libc.so.6
#9  0x00007f7e1544a06e in malloc_printerr () at /lib64/libc.so.6
#10 0x00007f7e1544ad86 in _int_free () at /lib64/libc.so.6
#11 0x00007f7e11aa92f2 in QMetaCallEvent::~QMetaCallEvent() (this=0x7f7df80033c0, __in_chrg=<optimized out>) at kernel/qobject.cpp:467
#12 0x00007f7e11aa9349 in QMetaCallEvent::~QMetaCallEvent() (this=0x7f7df80033c0, __in_chrg=<optimized out>) at kernel/qobject.cpp:476
#13 0x00007f7e11a7eae7 in QCoreApplication::removePostedEvents(QObject*, int) (receiver=0x1e66b70, eventType=eventType@entry=0) at kernel/qcoreapplication.cpp:1670
#14 0x00007f7e11aa98d7 in QObjectPrivate::~QObjectPrivate() (this=0x1e66ed0, __in_chrg=<optimized out>) at kernel/qobject.cpp:235
#15 0x00007f7e11aa9a19 in QObjectPrivate::~QObjectPrivate() (this=0x1e66ed0, __in_chrg=<optimized out>) at kernel/qobject.cpp:246
#16 0x00007f7e11ab3fb4 in QObject::~QObject() (pointer=<optimized out>) at ../../src/corelib/tools/qscopedpointer.h:54
#17 0x00007f7e11ab3fb4 in QObject::~QObject() (this=0x1e66b78, __in_chrg=<optimized out>) at ../../src/corelib/tools/qscopedpointer.h:101
#18 0x00007f7e11ab3fb4 in QObject::~QObject() (this=<optimized out>, __in_chrg=<optimized out>) at kernel/qobject.cpp:883
#19 0x00007f7e00cd2469 in QXcbConnection::~QXcbConnection() () at /usr/lib64/libQt5XcbQpa.so.5
#20 0x00007f7e00cd8eae in QXcbIntegration::~QXcbIntegration() () at /usr/lib64/libQt5XcbQpa.so.5
#21 0x00007f7e00cd8fa9 in QXcbIntegration::~QXcbIntegration() () at /usr/lib64/libQt5XcbQpa.so.5
#22 0x00007f7e11fc3775 in QGuiApplicationPrivate::~QGuiApplicationPrivate() () at /usr/lib64/libQt5Gui.so.5
#23 0x00007f7e1275b479 in QApplicationPrivate::~QApplicationPrivate() () at /usr/lib64/libQt5Widgets.so.5
#24 0x00007f7e11ab3fb4 in QObject::~QObject() (pointer=<optimized out>) at ../../src/corelib/tools/qscopedpointer.h:54
#25 0x00007f7e11ab3fb4 in QObject::~QObject() (this=0x7fffda3e3028, __in_chrg=<optimized out>) at ../../src/corelib/tools/qscopedpointer.h:101
#26 0x00007f7e11ab3fb4 in QObject::~QObject() (this=<optimized out>, __in_chrg=<optimized out>) at kernel/qobject.cpp:883
#27 0x00007f7e1275cffc in QApplication::~QApplication() () at /usr/lib64/libQt5Widgets.so.5
#28 0x00007f7e1579b25e in kdemain () at /usr/lib64/libkdeinit5_konsole.so
#29 0x00007f7e153f3b05 in __libc_start_main () at /lib64/libc.so.6
#30 0x00000000004007ee in _start ()

Reported using DrKonqi
Comment 1 Christoph Feck 2017-07-02 13:13:35 UTC
*** Bug 381878 has been marked as a duplicate of this bug. ***
Comment 2 Justin Zobel 2020-12-01 23:07:41 UTC
Thanks for the report.

As it's been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 3 stakanov.s 2020-12-01 23:32:32 UTC
Just closing it. After 5 years it is not worthwhile loosing my time.
Comment 4 Cezar Tigaret 2020-12-02 18:23:18 UTC
This issue is not occurring anymore.

Thank you