https://bugs.kde.org/show_bug.cgi?id=482274

            Bug ID: 482274
           Summary: Kate Segfaults when opening some files.
    Classification: Applications
           Product: kate
           Version: 24.02.0
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: application
          Assignee: kwrite-bugs-n...@kde.org
          Reporter: dashonww...@pm.me
  Target Milestone: ---

SUMMARY
Hey, just updated endeavourOS / arch using the testing repos, so hopefully this
isn't a packaging issue, but I have generated a backtrace for a couple
different files in which this has happened. I see what looks like it is
pointing to an issue with some plugin.


STEPS TO REPRODUCE
Kate has so many plugins and the number of combinations of plugins probably
make this hard to recreate with just reproduction steps, but anyways.
1. Open a file with kate from dolphin: in my case I am using fish shell
scripts. Some bash scripts have also had the issue, I can't really see a
pattern here.

OBSERVED RESULT
File will either never open or open briefly before closing the window.

EXPECTED RESULT
Kate window should open and stay open without crashing.

SOFTWARE/OS VERSIONS
Operating System: EndeavourOS 
KDE Plasma Version: 6.0.0
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel Version: 6.7.6-zen1-2-zen (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7C95
System Version: 1.0

ADDITIONAL INFORMATION
Here is a back trace that I generated, I believe I have all of the relevant
debug symbols donwloaded, but let me know If I got something wrong.

Thread 2.1 "kate" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff0512e80 (LWP 160567)]
Kate::TextRange::setRange (this=0x555556569ca0, range=..., attribute=<error
reading variable: Cannot access memory at address 0x2>) at
/usr/src/debug/ktexteditor/ktexteditor-6.0.0/src/buffer/katetextrange.cpp:154


154         setAttribute(attribute);
#0  Kate::TextRange::setRange (this=0x555556569ca0, range=..., attribute=Python
Exception <class 'gdb.MemoryError'>: Cannot access memory at address 0x2
#1  0x00007fffece13fb9 in existingColoredBracketForPos (close=..., open=...,
oldRanges=Python Exception <class 'gdb.error'>: value has been optimized out
<synthetic pointer>) at
/usr/src/debug/kate/kate-24.02.0/addons/rainbow-parens/rainbowparens_plugin.cpp:234
#2  RainbowParenPluginView::rehighlight (this=0x5555562a7a60, view=<optimized
out>) at
/usr/src/debug/kate/kate-24.02.0/addons/rainbow-parens/rainbowparens_plugin.cpp:417
#3  0x00007ffff6590ca9 in QtPrivate::QSlotObjectBase::call (a=0x7fffffffd6e8,
r=0x5555562a7a60, this=0x5555562a7be0, this=<optimized out>, r=<optimized out>,
a=<optimized out>) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobjectdefs_impl.h:433
#4  doActivate<false> (sender=0x5555562a7c00, signal_index=3,
argv=0x7fffffffd6e8) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:4039
#5  0x00007ffff65988bc in QSingleShotTimer::timeout (this=0x5555562a7c00) at
/usr/src/debug/qt6-base/build/src/corelib/Core_autogen/include/qtimer.moc:159
#6  QSingleShotTimer::timerEvent (this=0x5555562a7c00) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qtimer.cpp:332
#7  0x00007ffff657c236 in QObject::event (this=0x5555562a7c00,
e=0x7fffffffd8a0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qobject.cpp:1414
#8  0x00007ffff74f438b in QApplicationPrivate::notify_helper (this=<optimized
out>, receiver=0x5555562a7c00, e=0x7fffffffd8a0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:3296
#9  0x00007ffff6539818 in QCoreApplication::notifyInternal2
(receiver=0x5555562a7c00, event=0x7fffffffd8a0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1121
#10 0x00007ffff669efa6 in QCoreApplication::sendEvent (event=0x7fffffffd8a0,
receiver=<optimized out>) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qcoreapplication.cpp:1539
#11 QTimerInfoList::activateTimers (this=0x55555568d7a0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qtimerinfo_unix.cpp:507
#12 0x00007ffff67756dc in timerSourceDispatch (source=<optimized out>) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_glib.cpp:149
#13 0x00007ffff486cf69 in g_main_dispatch (context=0x7fffe8000ef0) at
../glib/glib/gmain.c:3476
#14 0x00007ffff48cb3a7 in g_main_context_dispatch_unlocked
(context=0x7fffe8000ef0) at ../glib/glib/gmain.c:4284
#15 g_main_context_iterate_unlocked.isra.0
(context=context@entry=0x7fffe8000ef0, block=block@entry=1,
dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:4349
#16 0x00007ffff486b162 in g_main_context_iteration (context=0x7fffe8000ef0,
may_block=1) at ../glib/glib/gmain.c:4414
#17 0x00007ffff67739c4 in QEventDispatcherGlib::processEvents
(this=0x5555555bb400, flags=...) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventdispatcher_glib.cpp:393
#18 0x00007ffff6543d6e in QEventLoop::processEvents (flags=...,
this=0x7fffffffdb70) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:100
#19 QEventLoop::exec (this=0x7fffffffdb70, flags=...) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qeventloop.cpp:182
#20 0x00007ffff653c2b8 in QCoreApplication::exec () at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/global/qflags.h:74
#21 0x00007ffff74f0f0a in QApplication::exec () at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/widgets/kernel/qapplication.cpp:2574
#22 0x000055555555ceb4 in main (argc=<optimized out>, argv=<optimized out>) at
/usr/src/debug/kate/kate-24.02.0/apps/kate/main.cpp:529

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to