vikramrajkumar

Apparently still happening: https://github.com/BitShares/bitshares/issues/1482

Related: https://github.com/BitShares/bitshares/issues/665

Related: https://github.com/BitShares/bitshares/issues/896

I have seen other reports of this as well.

Another report (unsure what version): https://bitsharestalk.org/index.php?topic=14313.msg187862#msg187862

Still happening: https://bitsharestalk.org/index.php?topic=15420.msg198917#msg198917 It doesn't seem like right now fc supports a good way to escape bad strings like the above.

Will assume this was the backend hanging due to a corrupted wallet db. @valzav For future reference, when linking to specific lines of code, hit 'y' to get a permanent...

I forgot about this; I have observed this behaviour myself. The normal unlock can get stuck on the 3 loading dots, but if you use the Go to My Accounts...

@cryptosig That appears to be an actual corruption of the wallet database--we have no mechanism for trying to repair that. Your best bet is probably to try restoring from backup.

Still happening in some cases: https://bitsharestalk.org/index.php/topic,15900.msg205125.html#msg205125