More than occasionally SourceGear DiffMerge hangs.

[jfreidin]

I've found on several occasions, when I run Diff (SourceGear DiffMerge), the window is blank, it is using a lot of CPU. It is hung and I have to kill it. It happens on certain pairs of file revisions, easy to reproduce.

[lbauer]

Can you send us those file versions so we can try to reproduce this?

Email support at sourcegear.com, ATTN Linda.

Let us know what version of Vault you are using.

[jfreidin]

[1/27/2007 8:55:38 AM] Version Check: This Vault client is version 3.5.1.4786
[1/27/2007 8:55:38 AM] Version Check: Your Vault server is version 3.5.1.4786
[1/27/2007 8:55:39 AM] Version Check: The following information was retrieved from the SourceGear website. No information was sent to SourceGear. You can disable this part of the version check from the Options dialog.
[1/27/2007 8:55:39 AM] Version Check: The most recent Vault release is version 3.5.1.4786

[lbauer]

How large are the files you're diffing? Does Diff/Merge come up eventually?

It might take a while to display the Diff/Merge windows if the files are large.

[jfreidin]

Version 135 is 3444 lines, 114698 characters.
Version 135 is 3152 lines, 100938 characters.
Contents are C++ (.cpp).

I tried it again and waited a couple of minutes. It did eventually show me something, but what I got was a correct left pane, and a garbage right pane with mostly little square symbols and other symbols. I have tried viewing each version of the file and they are both fine.

[jfreidin]

Hi. I've been getting ready to send you the files versions and I have some more information.

1) The problem seems specific to Windows Server 2003. When I diff the file versions on my Windows XP Professional machine, it works. I'm surprised I never noticed that before. I guess I never expected it. Do you support Windows Server 2003? In all other respects the Vault client appears to work the same on the two machines.

2) The problem seems specific to version 136 of the file. When I diff versions 135/136 the right hand pane is garbage. When I diff 136/137, the left hand pane is garbage. Other version combinations don't have the problem. I'm able to reproduce it using the saved versions of the files so if you have a Windows Server 2003 machine, you should also be able to reproduce it.

3) I used emacs to edit version 136 of the file, so there may be an extra newline at the end or something. I have no idea if that's an issue.

[lbauer]

The problem seems specific to Windows Server 2003. When I diff the file versions on my Windows XP Professional machine, it works.

That's interesting. Yes, we do support Windows 2003 Server. If you look at Help->Technical Support in the Vault Client on the two Vault Client machines, are they using the same version of the .NET Framework?

What else might be different about these two machines?