I get that problem too. I've found that when that happens if you go back to the thread and refresh the page then start a new reply it will not give the error again.