Thanks for the offer. You can safely remove your old history though, as I've found the root of the issue .

This bug is triggered when the number defined in CONFIG_FEATURE_EDITING_HISTORY, which is the maximum amount of history lines to be saved, is reached. This is 100 in busybox-power. The bug can be easily reproduced by executing "seq 1 100 > ~/.ash_history", which causes insta-stuck history

BusyBox 1.19.2 got released yesterday, so that's the version I'll be basing the fix on. I've already got a quick fix working here, but it won't be until this weekend before I'll have the time to push out a proper release plus fix, unfortunately. Until then, stay tuned!