The behavior is there for some weeks, and it's quite easy to reproduce: -go to KMail in Kontact -double click an email to open it in a new window -close that window using either Ctrl-W or by clicking the X in the title bar (choosing close in the menu of the subwindow is not sufficient) This results in the entire Kontact crashing somewhere in libQtWebEngineCore (I sadly cannot get a backtrace atm, maybe next week). I'm using openSUSE Tumbleweed, Qt is 5.11.1.
confirmed #4 0x00007f1a7b192b65 in content::RenderProcessHostImpl::ShutdownRequest() () at ../../3rdparty/chromium/content/browser/renderer_host/render_process_host_impl.cc:3765 #5 0x00007f1a7a91b0f5 in content::mojom::RendererHostStubDispatch::Accept(content::mojom::RendererHost*, mojo::Message*) () at ./gen/content/common/renderer_host.mojom.cc:491 #6 0x00007f1a7c5c4c8d in mojo::InterfaceEndpointClient::HandleValidatedMessage(mojo::Message*) () at ../../3rdparty/chromium/mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:419 #7 0x00007f1a7c5fd929 in AcceptOnProxyThread() () at ../../3rdparty/chromium/ipc/ipc_mojo_bootstrap.cc:789 #8 0x00007f1a7c5fd40e in Invoke<scoped_refptr<IPC::(anonymous namespace)::ChannelAssociatedGroupController> const&, mojo::Message> () at ../../3rdparty/chromium/base/bind_internal.h:211 #9 0x00007f1a7c5fd40e in MakeItSo<void (IPC::(anonymous namespace)::ChannelAssociatedGroupController::* const&)(mojo::Message), scoped_refptr<IPC::(anonymous namespace)::ChannelAssociatedGroupController> const&, mojo::Message> () at ../../3rdparty/chromium/base/bind_internal.h:294 #10 0x00007f1a7c5fd40e in RunImpl<void (IPC::(anonymous namespace)::ChannelAssociatedGroupController::* const&)(mojo::Message), std::tuple<scoped_refptr<IPC::(anonymous namespace)::ChannelAssociatedGroupController>, base::internal::PassedWrapper<mojo::Message> > const&, 0, 1>() () at ../../3rdparty/chromium/base/bind_internal.h:368 #11 0x00007f1a7bd456f8 in base::OnceCallback<void ()>::Run() && () at ../../3rdparty/chromium/base/callback.h:65 #12 0x00007f1a7bd456f8 in base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) () at ./../../3rdparty/chromium/base/debug/task_annotator.cc:55 #13 0x00007f1a7bd65f5a in base::internal::IncomingTaskQueue::RunTask(base::PendingTask*) () at ./../../3rdparty/chromium/base/message_loop/incoming_task_queue.cc:124 #14 0x00007f1a7bd65f5a in base::MessageLoop::RunTask(base::PendingTask*) () at ./../../3rdparty/chromium/base/message_loop/message_loop.cc:399 ---Type <return> to continue, or q <return> to quit--- #15 0x00007f1a7bd66a0f in base::MessageLoop::DeferOrRunPendingTask(base::PendingTask) () at ./../../3rdparty/chromium/base/message_loop/message_loop.cc:411 #16 0x00007f1a7bd66b8a in base::MessageLoop::DoWork() () at ./../../3rdparty/chromium/base/message_loop/message_loop.cc:455 #17 0x00007f1a7a70bb8d in QtWebEngineCore::(anonymous namespace)::MessagePumpForUIQt::handleScheduledWork (this=<optimized out>) at /usr/src/debug/libqt5-qtwebengine-5.11.1-3.6.x86_64/src/core/content_browser_client_qt.cpp:231 #18 0x00007f1a7a70bb8d in QtWebEngineCore::(anonymous namespace)::MessagePumpForUIQt::customEvent(QEvent*) (this=0x23a8340, ev=<optimized out>) at /usr/src/debug/libqt5-qtwebengine-5.11.1-3.6.x86_64/src/core/content_browser_client_qt.cpp:213 #19 0x00007f1a81760e7b in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #20 0x00007f1a820d74b1 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #21 0x00007f1a820deb00 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5 #22 0x00007f1a817373c9 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #23 0x00007f1a8173a3bb in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #24 0x00007f1a81789a83 in () at /usr/lib64/libQt5Core.so.5 #25 0x00007f1a76a8affe in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0 #26 0x00007f1a76a8b298 in () at /usr/lib64/libglib-2.0.so.0 #27 0x00007f1a76a8b32c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #28 0x00007f1a817890a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #29 0x00007f1a69cb5041 in () at /usr/lib64/libQt5XcbQpa.so.5 #30 0x00007f1a8173609b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5 #31 0x00007f1a8173e212 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5 #32 0x0000000000405f69 in main(int, char**) (argc=1, argv=0x7fffd9cfd838) at /data/kde/src/kontact/src/main.cpp:229
The funny thing is that I can't reproduce anymore after installing the debuginfo/debugsource packages
Created attachment 116010 [details] New crash information added by DrKonqi kontact (5.9.2) using Qt 5.11.2 - What I was doing when the application crashed: Open a mail in a new window an than close the window -- Backtrace (Reduced): #7 0x00007f10a6f76fd5 in content::RenderProcessHostImpl::ShutdownRequest () at ../../3rdparty/chromium/content/browser/renderer_host/render_process_host_impl.cc:3769 #8 0x00007f10a670b445 in content::mojom::RendererHostStubDispatch::Accept () at ./gen/content/common/renderer_host.mojom.cc:491 #9 0x00007f10a840ab55 in mojo::InterfaceEndpointClient::HandleValidatedMessage () at ../../3rdparty/chromium/mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:419 #10 0x00007f10a8446389 in AcceptOnProxyThread () at ../../3rdparty/chromium/ipc/ipc_mojo_bootstrap.cc:789 #12 MakeItSo<void (IPC::(anonymous namespace)::ChannelAssociatedGroupController::* const&)(mojo::Message), scoped_refptr<IPC::(anonymous namespace)::ChannelAssociatedGroupController> const&, mojo::Message> () at ../../3rdparty/chromium/base/bind_internal.h:294
*** Bug 399996 has been marked as a duplicate of this bug. ***
Created attachment 116072 [details] New crash information added by DrKonqi kmail (5.9.2) using Qt 5.11.2 - What I was doing when the application crashed: Double click on email in KMail, the corresponding email would open very briefly and then KMail would completely crash. No other program was running except the help file when this occured. -- Backtrace (Reduced): #7 0x00007fdf958c6505 in content::RenderProcessHostImpl::ShutdownRequest () at ../../3rdparty/chromium/content/browser/renderer_host/render_process_host_impl.cc:3769 #8 0x00007fdf9504e4f5 in content::mojom::RendererHostStubDispatch::Accept () at ./gen/content/common/renderer_host.mojom.cc:491 #9 0x00007fdf96cf8fad in mojo::InterfaceEndpointClient::HandleValidatedMessage () at ../../3rdparty/chromium/mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:419 #10 0x00007fdf96d31c49 in AcceptOnProxyThread () at ../../3rdparty/chromium/ipc/ipc_mojo_bootstrap.cc:789 #12 MakeItSo<void (IPC::(anonymous namespace)::ChannelAssociatedGroupController::* const&)(mojo::Message), scoped_refptr<IPC::(anonymous namespace)::ChannelAssociatedGroupController> const&, mojo::Message> () at ../../3rdparty/chromium/base/bind_internal.h:294
*** Bug 401394 has been marked as a duplicate of this bug. ***
*** Bug 401330 has been marked as a duplicate of this bug. ***
*** Bug 401183 has been marked as a duplicate of this bug. ***
*** Bug 400901 has been marked as a duplicate of this bug. ***
*** Bug 400697 has been marked as a duplicate of this bug. ***
*** Bug 400988 has been marked as a duplicate of this bug. ***
Is this problem in kontact or in kmail? I use only kmail and it's very prone to crash since last updates.
*** Bug 401826 has been marked as a duplicate of this bug. ***
*** Bug 401679 has been marked as a duplicate of this bug. ***
This problem is getting worse. It used to only happen for me when I clicked the trash icon directly from the email, but now it's starting to crash when I close the email window via the [X]. Not every time (yet), but enough that Kontact is becoming all but unusable.
(In reply to lnxusr from comment #15) > This problem is getting worse. It used to only happen for me when I clicked > the trash icon directly from the email, but now it's starting to crash when > I close the email window via the [X]. Not every time (yet), but enough that > Kontact is becoming all but unusable. Worse? Unusable? Kmail doesn't keep running a minute if i use it, it crashes in 20-40 seconds.
*** Bug 403625 has been marked as a duplicate of this bug. ***
*** Bug 404492 has been marked as a duplicate of this bug. ***
*** Bug 406253 has been marked as a duplicate of this bug. ***
*** Bug 406202 has been marked as a duplicate of this bug. ***
Thank you for reporting this crash in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the crash with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
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!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone!