Bug 389272 - Closing Konsole window caused crash
Summary: Closing Konsole window caused crash
Status: RESOLVED WORKSFORME
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 16.04.3
Platform: Mint (Ubuntu based) Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: drkonqi
: 389308 390429 391506 391643 391737 393184 (view as bug list)
Depends on:
Blocks:
 
Reported: 2018-01-21 08:36 UTC by kajitsu22
Modified: 2021-01-11 02:59 UTC (History)
9 users (show)

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


Attachments
New crash information added by DrKonqi (4.49 KB, text/plain)
2018-02-27 20:25 UTC, samurai.unname
Details
attachment-21210-0.html (1.66 KB, text/html)
2020-12-18 23:16 UTC, Paul Belanger
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kajitsu22 2018-01-21 08:36:19 UTC
Application: konsole (16.04.3)

Qt Version: 5.6.1
Frameworks Version: 5.36.0
Operating System: Linux 4.13.0-26-generic i686
Distribution: Linux Mint 18.3 Sylvia

-- Information about the crash:
- What I was doing when the application crashed:

  Just simply closed Konsole window, and catched this error. Don't know, what's this, but this is ridiculous, and should not be.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb08f6840 (LWP 2687))]

Thread 3 (Thread 0xaf9f8b40 (LWP 2689)):
[KCrash Handler]
#7  0xb7f08ce5 in __kernel_vsyscall ()
#8  0xb7d07ea9 in __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#9  0xb7d09407 in __GI_abort () at abort.c:89
#10 0xb7d4337c in __libc_message (do_abort=2, fmt=0xb7e3be54 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
#11 0xb7d492f7 in malloc_printerr (action=<optimized out>, str=0xb7e3bf94 "double free or corruption (fasttop)", ptr=<optimized out>, ar_ptr=0xaf000010) at malloc.c:5006
#12 0xb7d49c31 in _int_free (av=0xaf000010, p=<optimized out>, have_lock=0) at malloc.c:3867
#13 0xb45bc305 in ?? () from /usr/lib/nvidia-384/tls/libnvidia-tls.so.384.111
#14 0xb50e6400 in __nptl_deallocate_tsd () at pthread_create.c:175
#15 0xb50e7368 in __nptl_deallocate_tsd () at ../sysdeps/unix/sysv/linux/exit-thread.h:36
#16 start_thread (arg=0xaf9f8b40) at pthread_create.c:346
#17 0xb7dc30ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 2 (Thread 0xb08e5b40 (LWP 2688)):
#0  0xb4fe6488 in g_mutex_unlock () from /lib/i386-linux-gnu/libglib-2.0.so.0
#1  0xb4f9f5cb in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0xb4fa0024 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb4fa0254 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb6326234 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#5  0xb62cc2b6 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#6  0xb62cc6ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#7  0xb60fd82d in QThread::exec() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#8  0xb5a126ac in ?? () from /usr/lib/i386-linux-gnu/libQt5DBus.so.5
#9  0xb6102ad2 in ?? () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#10 0xb50e7295 in start_thread (arg=0xb08e5b40) at pthread_create.c:333
#11 0xb7dc30ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114

Thread 1 (Thread 0xb08f6840 (LWP 2687)):
#0  0xb7f08ce5 in __kernel_vsyscall ()
#1  0xb7db8ecf in poll () at ../sysdeps/unix/syscall-template.S:84
#2  0xb515541d in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1
#3  0xb51571fb in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1
#4  0xb5157359 in xcb_wait_for_reply () from /usr/lib/i386-linux-gnu/libxcb.so.1
#5  0xb54f5092 in _XReply () from /usr/lib/i386-linux-gnu/libX11.so.6
#6  0xb54f09af in XSync () from /usr/lib/i386-linux-gnu/libX11.so.6
#7  0xb54d12b1 in XCloseDisplay () from /usr/lib/i386-linux-gnu/libX11.so.6
#8  0xafae09bf in QXcbConnection::~QXcbConnection() () from /usr/lib/i386-linux-gnu/libQt5XcbQpa.so.5
#9  0xafae0d7a in QXcbConnection::~QXcbConnection() () from /usr/lib/i386-linux-gnu/libQt5XcbQpa.so.5
#10 0xafae286f in QXcbIntegration::~QXcbIntegration() () from /usr/lib/i386-linux-gnu/libQt5XcbQpa.so.5
#11 0xafae299a in QXcbIntegration::~QXcbIntegration() () from /usr/lib/i386-linux-gnu/libQt5XcbQpa.so.5
#12 0xb6605eaa in QGuiApplicationPrivate::~QGuiApplicationPrivate() () from /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5
#13 0xb6bfe783 in QApplicationPrivate::~QApplicationPrivate() () from /usr/lib/i386-linux-gnu/libQt5Widgets.so.5
#14 0xb6bfe80a in QApplicationPrivate::~QApplicationPrivate() () from /usr/lib/i386-linux-gnu/libQt5Widgets.so.5
#15 0xb6303e09 in QObject::~QObject() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#16 0xb62d083a in QCoreApplication::~QCoreApplication() () from /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5
#17 0xb6605c0d in QGuiApplication::~QGuiApplication() () from /usr/lib/i386-linux-gnu/sse2/libQt5Gui.so.5
#18 0xb6c006a2 in QApplication::~QApplication() () from /usr/lib/i386-linux-gnu/libQt5Widgets.so.5
#19 0xb7a153ff in KApplication::~KApplication() () from /usr/lib/i386-linux-gnu/libKF5KDELibs4Support.so.5
#20 0xb7a4c73f in KUniqueApplication::~KUniqueApplication() () from /usr/lib/i386-linux-gnu/libKF5KDELibs4Support.so.5
#21 0xb7ea06e2 in ?? () from /usr/lib/i386-linux-gnu/libkdeinit5_konsole.so
#22 0xb7eb3557 in kdemain () from /usr/lib/i386-linux-gnu/libkdeinit5_konsole.so
#23 0x08048567 in ?? ()
#24 0xb7cf4637 in __libc_start_main (main=0x8048540, argc=3, argv=0xbfc751f4, init=0x80486a0 <__libc_csu_init>, fini=0x8048700 <__libc_csu_fini>, rtld_fini=0xb7f19880 <_dl_fini>, stack_end=0xbfc751ec) at ../csu/libc-start.c:291
#25 0x08048595 in _start ()

The reporter indicates this bug may be a duplicate of or related to bug 378562, bug 379212.

Possible duplicates by query: bug 388951, bug 388364, bug 387393, bug 386607, bug 381268.

Reported using DrKonqi
Comment 1 Kurt Hindenburg 2018-01-21 21:37:45 UTC
I see a lot of crash reports with Qt5.6.x - try to update Qt and KDE if you can.
Comment 2 Ahmad Samir 2018-02-11 13:04:55 UTC
And also the nvidia-384 proprietary driver, might be a culprit...
Comment 3 Ahmad Samir 2018-02-11 13:16:16 UTC
384.90 to be precise.
Comment 4 Christoph Feck 2018-02-11 15:02:42 UTC
*** Bug 389308 has been marked as a duplicate of this bug. ***
Comment 5 samurai.unname 2018-02-27 20:25:15 UTC
Created attachment 111065 [details]
New crash information added by DrKonqi

konsole (16.04.3) using Qt 5.6.1

- What I was doing when the application crashed:

You are closing the konsole window after you finish compiling a program when you crash konsole

-- Backtrace (Reduced):
#6  0x00007f6a073e0428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7  0x00007f6a073e202a in __GI_abort () at abort.c:89
[...]
#9  0x00007f6a0742b37a in malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7f6a0753bfe8 "double free or corruption (out)", action=3) at malloc.c:5006
#10 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3867
#11 0x00007f6a0742f53c in __GI___libc_free (mem=<optimized out>) at malloc.c:2968
Comment 6 Kurt Hindenburg 2018-03-12 13:50:55 UTC
*** Bug 390429 has been marked as a duplicate of this bug. ***
Comment 7 Kurt Hindenburg 2018-03-12 13:51:18 UTC
*** Bug 391737 has been marked as a duplicate of this bug. ***
Comment 8 Kurt Hindenburg 2018-03-12 13:54:13 UTC
*** Bug 391506 has been marked as a duplicate of this bug. ***
Comment 9 Ahmad Samir 2018-03-25 15:40:10 UTC
*** Bug 391643 has been marked as a duplicate of this bug. ***
Comment 10 Ahmad Samir 2018-03-25 15:42:58 UTC
It might be worthwhile to update the nvidia driver on your system, as this crash seems to happen with version 384.11. Also to report the issue at https://devtalk.nvidia.com/default/board/98/ , as only the nvidia devs can have access to nvidia libs debug symbols being proprietary and all.
Comment 11 Nate Graham 2018-04-16 16:59:48 UTC
*** Bug 393184 has been marked as a duplicate of this bug. ***
Comment 12 Paul Belanger 2018-04-25 12:51:47 UTC
I have just experience the same issue when closing Konsole: 

Application: Konsole (konsole), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fbfd7cae940 (LWP 23363))]

Thread 2 (Thread 0x7fbfd5364700 (LWP 23364)):
#0  __lll_lock_wait_private () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:95
#1  0x00007fbfe9e472bd in _int_free (av=0x7fbfd0000020, p=0x7fbfd00009a0, have_lock=0) at malloc.c:3962
#2  0x00007fbfe9e4b53c in __GI___libc_free (mem=<optimized out>) at malloc.c:2968
#3  0x00007fbfe2389439 in __nptl_deallocate_tsd () at pthread_create.c:175
#4  0x00007fbfe238a870 in __nptl_deallocate_tsd () at pthread_create.c:326
#5  start_thread (arg=0x7fbfd5364700) at pthread_create.c:346
#6  0x00007fbfe9ece41d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fbfd7cae940 (LWP 23363)):
[KCrash Handler]
#6  0x00007fbfe9dfc428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#7  0x00007fbfe9dfe02a in __GI_abort () at abort.c:89
#8  0x00007fbfe9e3e7ea in __libc_message (do_abort=2, fmt=fmt@entry=0x7fbfe9f57ed8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
#9  0x00007fbfe9e457c3 in malloc_printerr (ar_ptr=0x7fbfd0000020, ptr=0x7fbfd0003fd0, str=0x7fbfe9f54c92 "corrupted double-linked list", action=<optimized out>) at malloc.c:5006
#10 malloc_consolidate (av=av@entry=0x7fbfd0000020) at malloc.c:4175
#11 0x00007fbfe9e47678 in _int_free (av=0x7fbfd0000020, p=<optimized out>, have_lock=0) at malloc.c:4075
#12 0x00007fbfe9e4b53c in __GI___libc_free (mem=<optimized out>) at malloc.c:2968
#13 0x00007fbfd76f2900 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#14 0x00007fbfd76c658b in QXcbConnection::~QXcbConnection() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#15 0x00007fbfd76c6ac9 in QXcbConnection::~QXcbConnection() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#16 0x00007fbfd76c8216 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#17 0x00007fbfd76c8329 in QXcbIntegration::~QXcbIntegration() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#18 0x00007fbfe6d7dcb3 in QGuiApplicationPrivate::~QGuiApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#19 0x00007fbfe7333089 in QApplicationPrivate::~QApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#20 0x00007fbfe6a7bb48 in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007fbfe7334e79 in QApplication::~QApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#22 0x00007fbfea1b8d9c in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_konsole.so
#23 0x00007fbfe9de7830 in __libc_start_main (main=0x400710 <main>, argc=1, argv=0x7fffa75b2308, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffa75b22f8) at ../csu/libc-start.c:291
#24 0x0000000000400749 in _start ()
Comment 13 Justin Zobel 2020-12-17 05:38:59 UTC
Thank you for the crash report.

As it has 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 have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 14 Paul Belanger 2020-12-18 23:16:46 UTC
Created attachment 134195 [details]
attachment-21210-0.html

Unfortunately I no longer have access to this machine to test.

On Thu., Dec. 17, 2020, 00:39 Justin Zobel, <bugzilla_noreply@kde.org>
wrote:

> https://bugs.kde.org/show_bug.cgi?id=389272
>
> Justin Zobel <justin.zobel@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>          Resolution|---                         |WAITINGFORINFO
>              Status|CONFIRMED                   |NEEDSINFO
>
> --- Comment #13 from Justin Zobel <justin.zobel@gmail.com> ---
> Thank you for the crash report.
>
> As it has 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 have set the bug status to "needsinfo" pending your response, please
> change
> back to "reported" or "resolved/worksforme" when you respond, thank you.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
Comment 15 Bug Janitor Service 2021-01-02 04:34:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 16 Christoph Feck 2021-01-09 16:46:46 UTC
Thanks for the update; changing status.
Comment 17 Kevin 2021-01-10 17:43:56 UTC
Remove me from the list please and thank you.

Kevin McErlean

> On Jan 9, 2021, at 10:46 AM, Christoph Feck <bugzilla_noreply@kde.org> wrote:
> 
> https://bugs.kde.org/show_bug.cgi?id=389272
> 
> Christoph Feck <cfeck@kde.org> changed:
> 
>          What    |Removed                     |Added
> ----------------------------------------------------------------------------
>            Status|NEEDSINFO                   |RESOLVED
>        Resolution|WAITINGFORINFO              |WORKSFORME
> 
> --- Comment #16 from Christoph Feck <cfeck@kde.org> ---
> Thanks for the update; changing status.
> 
> -- 
> You are receiving this mail because:
> You are on the CC list for the bug.
Comment 18 Christoph Feck 2021-01-11 02:59:27 UTC
Done. Next time, please remove yourself from bugs you no longer want to follow, or change your bugzilla settings.