Yikes. This sounds, however, like a completely different bug, if it is only triggered by unzipping archives. I'm sure that the situation is more complicated than it looks - because it looks like there is just a shocking lack of QA testing being done, if basic edge cases like this are resulting in undefined behavior.
Peter Bright at Ars Technica had an interesting article on the Windows development process, with a tidbit of information I thought was interesting. Apparently it's permitted to integrate code into Windows that doesn't have tests:
I expect there are automated tests, but it's been my experience that automated tests are usually not very deeply implemented. They often test the expected code paths, and new code, with new tests that fail to review the existing tests can often result in regressions that are not caught.
It's fine, because "automation" automatically finds all the bugs, and developers are evaluated primarily on code quality and test coverage, not on ability to crank out feature code as rapidly as possible.
