Bug 457355

Summary: Akregator crashes when attempting to open a link from the internal browser tab
Product: [Applications] akregator Reporter: John Apple II <jappleii>
Component: internal browserAssignee: kdepim bugs <kdepim-bugs>
Status: REPORTED ---    
Severity: crash CC: ben, edu.bugs.kde, mafosa
Priority: NOR Keywords: drkonqi
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description John Apple II 2022-08-01 02:53:42 UTC
Application: akregator (5.20.1 (22.04.1))

Qt Version: 5.15.5
Frameworks Version: 5.96.0
Operating System: Linux 5.18.13-200.fc36.x86_64 x86_64
Windowing System: X11
Distribution: "Fedora release 36 (Thirty Six)"
DrKonqi: 5.25.3 [KCrashBackend]

-- Information about the crash:
This is reproducible on my system.  

The news feed I'm loading is: https://www.linux.com/rss/
The page loaded in the internal browser from the feed is: https://www.linux.com/news/happy-sysadmin-appreciation-day-2022s-top-articles-for-sysadmins/
When selecting the "Read More" link (which ultimately redirects to https://www.redhat.com/sysadmin/sysadmin-day-2022), the crash notification appears and within 3s Akregator closes

The crash can be reproduced every time.

-- Backtrace:
Application: Akregator (akregator), signal: Segmentation fault

[KCrash Handler]
#4  0x0000558703a8e6e0 in ?? ()
#5  0x00007f8b4e17bed6 in content::WebContentsImpl::CreateNewWindow () at ../../3rdparty/chromium/content/browser/web_contents/web_contents_impl.cc:3759
#6  0x00007f8b4dfe3c70 in content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr<content::mojom::CreateNewWindowParams>, base::OnceCallback<void (content::mojom::CreateNewWindowStatus, mojo::StructPtr<content::mojom::CreateNewWindowReply>)>) () at ../../3rdparty/chromium/content/browser/renderer_host/render_frame_host_impl.cc:5077
#7  0x00007f8b4a26959a in content::mojom::FrameHostStubDispatch::AcceptWithResponder () at gen/content/common/frame.mojom.cc:7074
#8  0x00007f8b4dfbbb9d in content::mojom::FrameHostStub<mojo::RawPtrImplRefTraits<content::mojom::FrameHost> >::AcceptWithResponder () at gen/content/common/frame.mojom.h:1025
#9  content::mojom::FrameHostStub<mojo::RawPtrImplRefTraits<content::mojom::FrameHost> >::AcceptWithResponder () at gen/content/common/frame.mojom.h:1020
#10 0x00007f8b4bf52017 in mojo::InterfaceEndpointClient::HandleValidatedMessage () at ../../3rdparty/chromium/mojo/public/cpp/bindings/lib/interface_endpoint_client.cc:528
#11 0x00007f8b4bf527db in mojo::MessageDispatcher::Accept () at ../../3rdparty/chromium/mojo/public/cpp/bindings/lib/message_dispatcher.cc:46
#12 0x00007f8b4bf971a8 in AcceptSyncMessage () at ../../3rdparty/chromium/ipc/ipc_mojo_bootstrap.cc:987
#13 0x00007f8b4b8c6e3e in base::OnceCallback<void ()>::Run() && () at ../../3rdparty/chromium/base/callback.h:100
#14 base::TaskAnnotator::RunTask () at ./../../3rdparty/chromium/base/task/common/task_annotator.cc:163
#15 0x00007f8b4b8dbe34 in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWorkImpl () at ./../../3rdparty/chromium/base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:332
#16 0x00007f8b4b8dc33c in base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::DoWork () at ./../../3rdparty/chromium/base/task/sequence_manager/thread_controller_with_message_pump_impl.cc:252
#17 0x00007f8b49806088 in QtWebEngineCore::MessagePumpForUIQt::handleScheduledWork (this=0x55870315e8a0) at /usr/src/debug/qt5-qtwebengine-5.15.9-4.fc36.x86_64/src/core/browser_main_parts_qt.cpp:208
#18 0x00007f8b530d2155 in QObject::event (this=0x55870315e8b0, e=0x7f8aec2172f0) at kernel/qobject.cpp:1336
#19 0x00007f8b53daed22 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x55870315e8b0, e=0x7f8aec2172f0) at kernel/qapplication.cpp:3637
#20 0x00007f8b530a8228 in QCoreApplication::notifyInternal2 (receiver=0x55870315e8b0, event=0x7f8aec2172f0) at kernel/qcoreapplication.cpp:1064
#21 0x00007f8b530ab594 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x558702b6e380) at kernel/qcoreapplication.cpp:1821
#22 0x00007f8b530f9467 in postEventSourceDispatch (s=0x558702d2ce20) at kernel/qeventdispatcher_glib.cpp:277
#23 0x00007f8b51273faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#24 0x00007f8b512c92c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0
#25 0x00007f8b51271940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#26 0x00007f8b530f8f5a in QEventDispatcherGlib::processEvents (this=0x558702d36910, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#27 0x00007f8b530a6c7a in QEventLoop::exec (this=this@entry=0x7fff8ce419c0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#28 0x00007f8b530aed42 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#29 0x00007f8b5355fb70 in QGuiApplication::exec () at kernel/qguiapplication.cpp:1860
#30 0x00007f8b53daec99 in QApplication::exec () at kernel/qapplication.cpp:2829
#31 0x000055870296d89c in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/akregator-22.04.1-1.fc36.x86_64/src/main.cpp:115
[Inferior 1 (process 3761) detached]

The reporter indicates this bug may be a duplicate of or related to bug 426569, bug 443758.

Reported using DrKonqi
Comment 1 edu.bugs.kde 2022-11-30 13:08:25 UTC
Created attachment 154166 [details]
New crash information added by DrKonqi

akregator (5.21.1 (22.08.1)) using Qt 5.15.7

Reading this article in internal browser: https://www.linux.com/news/find-anything-you-need-with-fzf-the-linux-fuzzy-finder-tool/

I click the "Read More" link, which points to https://www.redhat.com/sysadmin/fzf-linux-fuzzy-finder

Akregator crashes.

-- Backtrace (Reduced):
#5  0x00007fdf24776776 in content::WebContentsImpl::CreateNewWindow(content::RenderFrameHost*, content::mojom::CreateNewWindowParams const&, bool, bool, content::SessionStorageNamespace*) () from /lib64/libQt5WebEngineCore.so.5
#6  0x00007fdf245de4d0 in content::RenderFrameHostImpl::CreateNewWindow(mojo::StructPtr<content::mojom::CreateNewWindowParams>, base::OnceCallback<void (content::mojom::CreateNewWindowStatus, mojo::StructPtr<content::mojom::CreateNewWindowReply>)>) () from /lib64/libQt5WebEngineCore.so.5
#7  0x00007fdf2086690a in content::mojom::FrameHostStubDispatch::AcceptWithResponder(content::mojom::FrameHost*, mojo::Message*, std::unique_ptr<mojo::MessageReceiverWithStatus, std::default_delete<mojo::MessageReceiverWithStatus> >) () from /lib64/libQt5WebEngineCore.so.5
#8  0x00007fdf245b635d in content::mojom::FrameHostStub<mojo::RawPtrImplRefTraits<content::mojom::FrameHost> >::AcceptWithResponder(mojo::Message*, std::unique_ptr<mojo::MessageReceiverWithStatus, std::default_delete<mojo::MessageReceiverWithStatus> >) () from /lib64/libQt5WebEngineCore.so.5
#10 0x00007fdf2254e52b in mojo::MessageDispatcher::Accept(mojo::Message*) () from /lib64/libQt5WebEngineCore.so.5
Comment 2 Ben Bonacci 2023-02-16 10:34:33 UTC
As of version 5.22.2 (22.12.2) I'm unable to reproduce your issue, even with the same URL mentioned. It's likely that the bug has been fixed in a later version, however this should be confirmed before closing just in case.