Bug 509662

Summary: Application hang when trying to edit a message
Product: [Applications] NeoChat Reporter: Evan Maddock <maddock.evan>
Component: GeneralAssignee: Tobias Fella <fella>
Status: REPORTED ---    
Severity: crash CC: carl, joseffribble, josh, kdedev
Priority: NOR    
Version First Reported In: 25.08.1   
Target Milestone: ---   
Platform: Solus   
OS: Linux   
URL: https://crash-reports.kde.org/organizations/kde/issues/256142/
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: The Neochat window state while frozen
The view of my system while NeoChat was unresponsive

Description Evan Maddock 2025-09-19 02:51:44 UTC
Created attachment 185066 [details]
The Neochat window state while frozen

SUMMARY
When clicking the inline toolbar to edit one of my messages in a room, Neochat completely froze. Upon opening the System Monitor, I noticed that it was using 4.1% of my CPU, which means it's pegging a CPU thread on my hardware. Over time, the memory usage also climbs, increasing by 2 GB in about 7 minutes.

STEPS TO REPRODUCE
1. Enter a room
2. Send a message
3. Wait for someone to start typing (unsure if this is required yet)
4. Hover over your message and click the "Message menu" button
5. Click the "Edit" button

OBSERVED RESULT
The application UI completely freezes and cannot be interacted with.

EXPECTED RESULT
The application UI would remain responsive, and my previous chat message turns into the editing state.

SOFTWARE/OS VERSIONS
Operating System: Solus 4.7
KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.5-322.current (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor
Memory: 64 GiB of RAM (62.7 GiB usable)
Graphics Processor: AMD Radeon RX 6600

ADDITIONAL INFORMATION
A couple of crash reports were generated and automatically sent to Sentry.
Comment 1 Evan Maddock 2025-09-19 02:52:36 UTC
Created attachment 185067 [details]
The view of my system while NeoChat was unresponsive
Comment 2 Evan Maddock 2025-09-19 02:55:14 UTC
I highly suspect that the typing indicator being visible is required to reproduce this. I cannot get it to happen without it.