Sencha have been claiming this issue as fixed for some time now, and the reported issue is not necessarily the issue reported by @ping, but a side issue.
So, assuming Sencha is right and closing the issue as it is not really clear how to reproduce it.
If you happen to be able to reproduce this issue, let us know and we'll reopen it.
