And you're importing & clearing the Rename-Pairs in between changing the .TXT file format?
Yes. Including "closing" the app because it closes itself when it encounters this error. Also manually closed it after each test.
We think Luuk's example helps clarify and it seems they are reproducing this bug as well.
Looking at the literally "blank" file in hex that cause the crash, it is pretty clearly related to it being this:
FE FF 00
0ASo it starts with FE FF but then only does 0A to finish with. If it was a Windows UTF-8 text file, it would read:
0A0D and that's it.
If you then open that file then save it as UNIX UTF-16, it turns into FE FF 0A 0D 00 0D 00 0A which then crashes.
Basically it is ending in a typical UNIX way but BRU doesn't seem to quite be handling the last line properly if it is only a UNIX based 0A and nothing else. It is expecting 0A then 0D and it doesn't see it so it crashes. In a UNIX file though, the 0D is not going to be there.
Even if it either said "check your file because it has an extra UNIX line" or just assumed it was there not on purpose would be an upgrade to the entire program (and possibly everything that was entered in already) crashing. Potentially midway through a project.
If you make a text file that is literally 4 bytes (
FE FF 00 0A) and save it as an actually UNIX file (or literally just those 4 bytes) and then try to import it, you will likely see the crash. We are technically one version away from the latest version but don't see anything in the changelog about it so don't think it is related but if you don't see it crash when you import that, might be missing something on our end we can look into more. Thank you for looking into this!