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.
Created attachment 185067 [details] The view of my system while NeoChat was unresponsive
I highly suspect that the typing indicator being visible is required to reproduce this. I cannot get it to happen without it.