Interesting. If you wouldn't mind posting this bug report in the client section you might be able to get some better feedback. This bug was supposedly fixed by the client devs several months ago, but it would appear that is has cropped up again.
Do you get any sort of error report when this occurs?