Although there will be a new client soon (hopefully) such a bug shouldn´t be left in the current client. Can´t you try to debug it CfB?
I would if I knew how to reproduce this situation.
I bet i know the real reason for this. I had this issue also (transaction was sent to another account).
So, after i clicked "send", the GUI waited too long. Finally it said "sent". Then i checked blocks tab and found wrong recent blocks number, unconfirmed transactions and other signs of freezed java process. I instantly logged into the server and found several exceptions (not related to timeout) in the log. Few minutes later daemon died by not enough memory exception.
Instead of that useless CRC checks, it's better first to implement an additional check that the process itself is heathly and can be used to transfer money. Right, just few integrity checks before NXT transfer execution. It's Java. It's cross-platform. It's terrible and not really your friend.
Right. Code that sends money is very simple.
So it's 100% prone to memory corruption? Come on...
Yes.