Bug 511952 - Crash when reporting a message
Summary: Crash when reporting a message
Status: RESOLVED UPSTREAM
Alias: None
Product: NeoChat
Classification: Applications
Component: General (other bugs)
Version First Reported In: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Tobias Fella
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2025-11-11 11:30 UTC by Nicolas Fella
Modified: 2025-12-01 15:44 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report: https://crash-reports.kde.org/organizations/kde/issues/292404/events/300f6571636a4aa286cc93918b6bf89b/


Attachments
New crash information added by DrKonqi (120.80 KB, text/plain)
2025-11-11 11:30 UTC, Nicolas Fella
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas Fella 2025-11-11 11:30:05 UTC
Application: neochat (26.03.70)
 (Compiled from sources)
ApplicationNotResponding [ANR]: false
Qt Version: 6.10.1
Frameworks Version: 6.20.0
Operating System: Linux 6.17.7-300.fc43.x86_64 x86_64
Windowing System: Wayland
Distribution: "Fedora Linux 43 (KDE Plasma Desktop Edition)"
DrKonqi: 6.5.80 [CoredumpBackend]

-- Information about the crash:
Right click on a message > Report > Report

The crash can be reproduced every time.

-- Backtrace (Reduced):
#4  std::__atomic_base<QReadWriteLockPrivate*>::load (this=0x30, __m=std::memory_order_relaxed) at /usr/include/c++/15/bits/atomic_base.h:828
#5  std::atomic<QReadWriteLockPrivate*>::load (this=0x30, __m=std::memory_order_relaxed) at /usr/include/c++/15/atomic:587
#6  QAtomicOps<QReadWriteLockPrivate*>::loadRelaxed<QReadWriteLockPrivate*> (_q_value=<error reading variable: Cannot access memory at address 0x30>) at /home/nico/workspace/qt6/qtbase/src/corelib/thread/qatomic_cxx11.h:203
#7  QBasicAtomicPointer<QReadWriteLockPrivate>::loadRelaxed (this=0x30) at /home/nico/workspace/qt6/qtbase/src/corelib/thread/qbasicatomic.h:171
#8  QReadWriteLock::tryLockForRead (this=0x30, timeout=...) at /home/nico/workspace/qt6/qtbase/src/corelib/thread/qreadwritelock.cpp:195
#9  0x00007f9a10d955a6 in QReadWriteLock::lockForRead (this=0x30) at /home/nico/workspace/qt6/qtbase/src/corelib/thread/qreadwritelock.h:69
#10 QReadLocker::relock (this=<synthetic pointer>) at /home/nico/workspace/qt6/qtbase/src/corelib/thread/qreadwritelock.h:116
#11 QReadLocker::QReadLocker (this=<synthetic pointer>, areadWriteLock=0x30) at /home/nico/workspace/qt6/qtbase/src/corelib/thread/qreadwritelock.h:135
#12 QtWaylandClient::QWaylandWindow::wlSurface (this=0x0) at /home/nico/workspace/qt6/qtbase/src/plugins/platforms/wayland/qwaylandwindow.cpp:971
#13 0x00007f9a10d6c237 in QtWaylandClient::QWaylandInputContext::setFocusObject (this=0x15ee6ec0, object=<optimized out>) at /home/nico/workspace/qt6/qtbase/src/plugins/platforms/wayland/qwaylandinputcontext.cpp:196
#14 0x00007f9a173e919c in QGuiApplicationPrivate::_q_updateFocusObject (this=this@entry=0x15dff550, object=0x166b2800) at /home/nico/workspace/qt6/qtbase/src/gui/kernel/qguiapplication.cpp:4544
#15 0x00007f9a173ff021 in QGuiApplicationPrivate::processFocusWindowEvent (e=<optimized out>) at /home/nico/workspace/qt6/qtbase/src/gui/kernel/qguiapplication.cpp:2739
#16 0x00007f9a1746727b in QWindowSystemInterface::sendWindowSystemEvents (flags=flags@entry=...) at /home/nico/workspace/qt6/qtbase/src/gui/kernel/qwindowsysteminterface.cpp:1117
#17 0x00007f9a17467497 in QWindowSystemInterface::flushWindowSystemEvents (flags=...) at /home/nico/workspace/qt6/qtbase/src/gui/kernel/qwindowsysteminterface.cpp:1086
#18 0x00007f9a16bff15c in QObject::event (this=<optimized out>, e=<optimized out>) at /home/nico/workspace/qt6/qtbase/src/corelib/kernel/qobject.cpp:1413
#19 0x00007f9a17f96a58 in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0x15e7dad0, e=0x7f99f4002f60) at /home/nico/workspace/qt6/qtbase/src/widgets/kernel/qapplication.cpp:3305


Reported using DrKonqi
Comment 1 Nicolas Fella 2025-11-11 11:30:06 UTC
Created attachment 186693 [details]
New crash information added by DrKonqi

DrKonqi auto-attaching complete backtrace.
Comment 3 Nicolas Fella 2025-12-01 15:44:00 UTC
Fixed upstream