Bug 453942 - fac27b49172fa3bbdfe3dbee0ceabe95b7c84b45 causes KRunner to crash on launch
Summary: fac27b49172fa3bbdfe3dbee0ceabe95b7c84b45 causes KRunner to crash on launch
Status: RESOLVED FIXED
Alias: None
Product: frameworks-kdeclarative
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: Arjen Hiemstra
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2022-05-17 16:57 UTC by Nate Graham
Modified: 2022-05-18 13:19 UTC (History)
1 user (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 Nate Graham 2022-05-17 16:57:15 UTC
With https://invent.kde.org/frameworks/kdeclarative/-/commit/fac27b49172fa3bbdfe3dbee0ceabe95b7c84b45, KRunner reproducibly crashes on launch for me with the following backtrace:

Thread 1 "krunner" received signal SIGSEGV, Segmentation fault.
QQmlEngine::rootContext (this=0x0) at qml/qqmlengine.cpp:1108
Downloading source file /usr/src/debug/qt5-qtdeclarative-5.15.3-2.fc36.x86_64/src/qml/qml/qqmlengine.cpp...
1108        return d->rootContext;
(gdb) bt
#0  QQmlEngine::rootContext (this=0x0) at qml/qqmlengine.cpp:1108
#1  0x00007ffff7d37323 in KDeclarative::QmlObject::QmlObject (this=0x796580, 
    engine=std::shared_ptr<QQmlEngine> (use count 1, weak count 0) = {...}, rootContext=0x0, 
    parent=<optimized out>) at /usr/include/c++/12/bits/shared_ptr_base.h:1665
#2  0x00007ffff7d375e0 in KDeclarative::QmlObject::QmlObject (this=0x796580, engine=0x0, 
    rootContext=0x0, parent=0x7fffffffd7e0)
    at /home/nate/kde/src/kdeclarative/src/kdeclarative/qmlobject.cpp:146
#3  0x000000000040b6df in View::View (this=this@entry=0x7fffffffd7e0)
    at /home/nate/kde/src/plasma-workspace/krunner/view.cpp:71
#4  0x0000000000408199 in main (argc=<optimized out>, argv=<optimized out>)
    at /home/nate/kde/src/plasma-workspace/krunner/main.cpp:85


If I go back to the commit right before it, the crash is fixed.
Comment 2 Nate Graham 2022-05-18 13:19:02 UTC
Confirmed, fixed now!