Open droidmonkey opened 1 year ago
When the CSV file is NOT in UTF-16, the CSV parser will enter an infinite read loop if UTF-16 is chosen as a codec.
The parser would not enter an infinite loop
I cannot reproduce it with KeePassXC 2.7.8, using some test CSVs I had lying around. Does it depend on the specific CSV file?
Make sure it doesn't have a BOM in the first two bytes?
Overview
When the CSV file is NOT in UTF-16, the CSV parser will enter an infinite read loop if UTF-16 is chosen as a codec.
Steps to Reproduce
Expected Behavior
The parser would not enter an infinite loop