Bug 456863 - Crash oldMarker > newMarker
Summary: Crash oldMarker > newMarker
Status: RESOLVED MOVED
Alias: None
Product: NeoChat
Classification: Applications
Component: General (other bugs)
Version First Reported In: unspecified
Platform: Flatpak Linux
: NOR crash
Target Milestone: ---
Assignee: Tobias Fella
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-18 16:09 UTC by Jan Bidler
Modified: 2022-11-27 18:05 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Bidler 2022-07-18 16:09:01 UTC 
SUMMARY
By rapidly editing a message, it's possible to crash NeoChat

STEPS TO REPRODUCE
1. Send a message in a room (I choose 🎆, not sure if it works with others)
2. Rapidly spam up arrow and Enter

OBSERVED RESULT
NeoChat crashes with the following line (no stacktrace produced):
ASSERT: "oldMarker > newMarker" in file /run/build/libQuotient/lib/eventstats.cpp, line 59
[Inferior 1 (process 62538) exited with code 0206]

EXPECTED RESULT
NeoChat should not crash

SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.5
NeoChat: self-compiled flatpak
Comment 1 Jan Bidler 2022-07-18 16:29:33 UTC 
Apparently editing a message is not even necessary; rapidly sending quick messages is enough (just tested via spam sending "#")
Comment 2 Jan Bidler 2022-08-09 18:00:46 UTC 
Wanted to add, that recently I got this crash by... just not doing anything. was trying to read messages in a room, and then it suddenly crashed that way.
Comment 3 Tobias Fella 2022-11-17 20:49:52 UTC 
Reported upstream: https://github.com/quotient-im/libQuotient/issues/588
Comment 4 Tobias Fella 2022-11-27 18:05:22 UTC 
Closing as it's an upstream bug