I think you may be seeing a different issue that just happens to have a similar sympotom. Please open a new bug. This particular issue is fixed by the referenced patch.