You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 10, 2024. It is now read-only.
Someone pasted some Zalgo'd text into a chatroom I was talking in just now, and HexChat decided to cease drawing all text properly, as seen in this screenshot:
This is the offending text from the chat logs, in case you don't know what "zalgo" is.
I had to restart HexChat in order to fix this. I don't know if the zalgoed text scrolling off the screen would have fixed it or not. Regardless of whether the font set in the settings supports unicode properly or not, this seems like a pretty serious problem.
Using HexChat version 2.10.2 on Windows 7 SPI, x64. The main font is set to "Consolas 10", which I'm pretty sure is the default, non-unicode-supporting font.
The text was updated successfully, but these errors were encountered:
Consolas contains many non-ASCII glyphs, including the ones in your sample.
More importantly Zalgo is made using combining characters, so it depends on the ability of the layout engine to render it and not any particular font's glyphs.
From your description, the offending text is still in view, which means text before it is also being misrendered? (Don't have HC in front of me to test at the moment.)
Edit: This might also be the buffer overflow for long lines that richtroye recently fixed.
The text before it was not being misrendered when the lines initially appeared. But when I moved my cursor over the lines before it, presumably it repainted those lines, as they too became corrupted. The rest of the UI elements became corrupted shortly after the offending lines appeared in chat.
I should also note, now that think about it: I have a second computer that sits in that chatroom just monitoring it all the time with HexChat 2.10.1, and this second computer's HexChat is not currently corrupted (the client untouched until hours after the incident). So it seems this bug can be recovered from without restarting the application (assuming it happened in 2.10.1).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Someone pasted some Zalgo'd text into a chatroom I was talking in just now, and HexChat decided to cease drawing all text properly, as seen in this screenshot:
This is the offending text from the chat logs, in case you don't know what "zalgo" is.
I had to restart HexChat in order to fix this. I don't know if the zalgoed text scrolling off the screen would have fixed it or not. Regardless of whether the font set in the settings supports unicode properly or not, this seems like a pretty serious problem.
Using HexChat version 2.10.2 on Windows 7 SPI, x64. The main font is set to "Consolas 10", which I'm pretty sure is the default, non-unicode-supporting font.
The text was updated successfully, but these errors were encountered: