Version Compare Zip bug

[Michael Bulgrien]

Currently one can edit the path on one side of a version compare and press enter to compare the other side's version info against a different version of the same file in a new location.

However, when the new location is a subfolder within a large zip file on a remote machine, this action sometimes fails with a red (X) error in the status bar. After several such failures, BC3 (build 463) can actually hang and have to be cancelled via Task Manager.

Note: Opening the new zip in a folder compare session and selecting the file from there does launch the version compare dialog just fine, so it is not a problem with a corrupt zip file. It appears to be a problem with finding the new dll in the new zip file when the zip file has not yet been opened in a folder compare session.

On a related note, when a saved version compare session includes a file in an imbedded sub folder within a zip file on a remote machine, re-opening the session from the home screen can error with a red (X) error in the status bar. Once the archive is opened in a folder compare session, the saved version compare session can be loaded without error.

[Chris]

Michael,

Thanks for reporting the problem. How large is the zip file you are comparing? Is the remote system on a local network, or does it have a slower network connection?

[Michael Bulgrien]

The zip files are on a local network (100 Mb Full Duplex) and are source code archives that are just under 150 MB in size.

Edit: Here is a screencast (http://screencast.com/t/9uOVSYbh) where I attempt to load a saved version compare session in a zip file. It errors.
When I open the parent in a new session then double-click the same files, the version compare is successful.

[Michael Bulgrien]

With the announcement that today's build may be the last "beta" release, I was curious if "Scooter" saw my screencast above and whether or not this problem could be repro'd in-house?

[Michael Bulgrien]

I've copied the zip files locally to my system and the initial version compare (opened from a saved session) consistently fails (every time, not sporadically). This rules out the remote machine and the network connection.

When I remove all other files from the zip file, then opening the version compare from a saved session works fine. This seems to indicate that BC3 cannot handle the size and/or folder tree complexity of the original zip files unless the zip files are already open in a folder compare session.

Edit: On my first attempt to open the saved session, the error shows up at the bottom of the screen after about 4 seconds. If I click the reload button on the toolbar, then BC3 spins for another 4 to 6 seconds then successfully opens up the version compare. Is there logic that causes the initial attempt to "time out" if the file is not found right away? I'm wondering if the plug-in that you are using to process zip files is prematurely returning a not-found error code.

[Michael Bulgrien]

This error still occurs in the "official release" build 8507.

[Craig]

I can reproduce this and it should be fixed in the next release.