Application: kate (24.02.0) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.7.9-arch1-1 x86_64 Windowing System: Wayland Distribution: EndeavourOS DrKonqi: 6.0.1 [CoredumpBackend] -- Information about the crash: When, either: A file containing brackets is opened with the colored brackets plugin enabled, or The colored brackets plugin is enabled while a file containing brackets is open, Kate crashes. The crash can be reproduced every time. -- Backtrace (Reduced): #5 std::__atomic_base<int>::fetch_add (__m=std::memory_order_acq_rel, __i=1, this=0x1fe238f0710, this=<optimized out>, __i=<optimized out>, __m=<optimized out>) at /usr/include/c++/13.2.1/bits/atomic_base.h:633 #6 QAtomicOps<int>::ref<int> (_q_value=<error reading variable: Cannot access memory at address 0x1fe238f0710>, _q_value=<optimized out>) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/thread/qatomic_cxx11.h:258 [...] #10 QArrayDataPointer<char16_t>::QArrayDataPointer (other=<optimized out>, this=0x5dfe231a0d68, this=<optimized out>, other=<optimized out>) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/tools/qarraydatapointer.h:40 #11 QString::QString (other=<optimized out>, this=0x5dfe231a0d68, this=<optimized out>, other=<optimized out>) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/text/qstring.h:1107 #12 QtPrivate::QMetaTypeForType<QString>::getCopyCtr()::{lambda(QtPrivate::QMetaTypeInterface const*, void*, void const*)#1}::operator()(QtPrivate::QMetaTypeInterface const*, void*, void const*) const (other=<optimized out>, addr=0x5dfe231a0d68, __closure=0x0) at /usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.2/src/corelib/kernel/qmetatype.h:2419 Reported using DrKonqi
Created attachment 167487 [details] New crash information added by DrKonqi DrKonqi auto-attaching complete backtrace.
The backtrace says otherwise. Would it be possible for you to share the file which causes the crash?
Created attachment 167491 [details] The file in question Absolutely; attached.
(In reply to nathan from comment #3) > Created attachment 167491 [details] > The file in question > > Absolutely; attached. Okay, this is strange: I just opened the file by double clicking it, and no crash occurred. What I had been doing before was opening a session that contained the file; when I did so, this file opened by default. When I turned on the plugin after opening the session, Kate crashed every time. Now that I have opened the file by double clicking it (rather than it opening by default when I resume a session), I can turn on the plugin and Kate does not crash when displaying the file, even when opened via a session.
If you see this again in future or find a way to reproduce the issue feel free to reopen / create a new bug. For now I think keeping this open is not useful. Thanks for reporting