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
Open a file whose filename is invalid utf8, which contains invalid utf8, so xi-core exits.
in my case, the filename is: (hex) 20 ed 96 4f 56 (or escaped): " \xed\x96OV"
the file is a corrupt stack trace that contains some non-utf8 gibberish, but any binary file should work.
After xi-core exits, xi-gtk enters an infinite loop printing error messages to the console
The infinite loop should be fixed in 39d5559. Filenames that are invalid UTF-8 are hard to support with the current architecture as the front-end communicates with the core through JSON and the JSON has to be valid UTF-8. Support for files whose content uses a non-UTF-8 encoding is something that should be handled in the core.
Support for non-utf8 filenames would be possible if annoying, but is probably something xi-core should support eventually. It means paths are going to need to be sent in base64 or something. I'd welcome an issue in xi-core but I don't expect to get around to it in a hurry.
Better support for non-utf8 encodings is definitely important, and there's been some very preliminary groundwork in this direction in core. I also don't think there's a real issue up for that, so again file in xi-core if you like @mateon1 :)
How to reproduce:
in my case, the filename is: (hex)
20 ed 96 4f 56
(or escaped):" \xed\x96OV"
the file is a corrupt stack trace that contains some non-utf8 gibberish, but any binary file should work.
Stdout/stderr:
The spam of Json-CRITICAL errors continues forever. The only solution is to kill xi-gtk.
The text was updated successfully, but these errors were encountered: