This bug slipped through because we are not able to reproduce it on our machines. I did, however, make a slight change in 2.3.1 that I hope has fixed the problem.

Do you guys still get this problem with LimeWire 2.3.1? Thanks, and our apologies for the frustration.