Often running SourceGear Vault client temporarily frozen
Moderator: SourceGear
Often running SourceGear Vault client temporarily frozen
I find that often when I click on a running SourceGear Vault client via the taskbar, or alt-tab to it, it appears frozen. Actually, it seems to happen every time.
That is, a huge white rectangle covers the screen, and after a while it paints the tree on the left and the file listings on the right.
MS-Outlook is the only other application that I can think of that seems to routinely freeze up like that when not being used.
I don't know if it is buggy, or just very, very sluggish, but it's certainly unattractive.
Vault Client version 3.1.6 (3658)
running on Windows XP SP2
That is, a huge white rectangle covers the screen, and after a while it paints the tree on the left and the file listings on the right.
MS-Outlook is the only other application that I can think of that seems to routinely freeze up like that when not being used.
I don't know if it is buggy, or just very, very sluggish, but it's certainly unattractive.
Vault Client version 3.1.6 (3658)
running on Windows XP SP2
Check the memory usage when you maximize the client -- maybe its temporarily using more memory. It could also be something to do with your video card or driver. We haven't had other reports of this, so it's something specific to your Vault Client machine.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Same thing I reported
This is the same condition as the frequent lockup issue I reported. Two of our developers experience this many times per day, and the rest don't. CTRL-ALT-Delete and then locking/unlocking your computer will put it into this state every time, but I have been unable to determine the conditions that make these two computers different than the rest. Both affected computers have gone through a clean OS install within the past few months.
Perry, are you using the 2.0 framework as well? (Check Help->Technical Support).
You both might want to turn on Vault client logging and see whether the hang seems to be happening within a particular Vault call or not. See http://support.sourcegear.com/viewtopic.php?t=1534 and turn on all classes. Note that you'll want to turn this off as soon as you reproduce the issue, as logging all classes generates huge amounts of data over time.
Also, if you are using the 2.0 framework, temporarily switching to the 1.1 framework would be helpful in determining whether the problem is related to the framework. See http://support.sourcegear.com/viewtopic.php?t=4354
You both might want to turn on Vault client logging and see whether the hang seems to be happening within a particular Vault call or not. See http://support.sourcegear.com/viewtopic.php?t=1534 and turn on all classes. Note that you'll want to turn this off as soon as you reproduce the issue, as logging all classes generates huge amounts of data over time.
Also, if you are using the 2.0 framework, temporarily switching to the 1.1 framework would be helpful in determining whether the problem is related to the framework. See http://support.sourcegear.com/viewtopic.php?t=4354
Help About output
BTW, as I've yet again rediscovered just now, the forum still has the bug that makes it fail for every post apparently: "You must select a topic to reply to".
Could you pass that on to whoever is responsible for the forum bugs, if anyone is?
Here is the text from the Help About you requested:
Client Information
Vault Client Version: 3.1.6.3658
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 511 MB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)
Server Information
Vault Server Version: 3.1.6.3658
.Net Framework Version: 1.1.4322.2300
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 1.0
OS Version: 5.2.3790
Timezone: (GMT-05:00) Eastern Time (US & Canada)
SQL Version: Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
Could you pass that on to whoever is responsible for the forum bugs, if anyone is?
Here is the text from the Help About you requested:
Client Information
Vault Client Version: 3.1.6.3658
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 511 MB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)
Server Information
Vault Server Version: 3.1.6.3658
.Net Framework Version: 1.1.4322.2300
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 1.0
OS Version: 5.2.3790
Timezone: (GMT-05:00) Eastern Time (US & Canada)
SQL Version: Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
I think I know what might be causing this. You have to log into the forum in order to post. If you're not logged in when you hit "Reply," you are redirected to a login screen. But when you login, the forum doesn't remember what post you wanted to reply to, so it says you need to pick a topic.BTW, as I've yet again rediscovered just now, the forum still has the bug that makes it fail for every post apparently: "You must select a topic to reply to".
A couple ways to avoid this message:
-- login before you use the forum
-- the next time you login, check the box for "automatically log me in each visit." You need to do this on each computer you're using.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
Are you logged in when responding to posts? If not, then you will have to log in. Also, you can set the login cookie to always remember to log in.Perry wrote:I have to admit that my preference would be for you all to fix the forum bug, instead of me adopting any of those workarounds on every computer.
Note, after removing the cookies (from a couple of posts up), shutting down the browser and coming back to the site, click the Log In link at the top. Use the Option to remember your login for subsequent visits.
Jeff Clausius
SourceGear
SourceGear
Test results
(bug "You must select a topic to reply to" just occurred)
> I just checked our server logs. It appears you're using FireFox 1.5. Is that correct?
It might have been back then; I'm now using what I hope is the latest and greatest: Firefox 1.5.0.1
> Can you clear any support.sourcegear.com cookies from FireFox's Cookie Manager and try again. I want to know if that solves the forum's issue.
All my sourcegear cookies expire at end of session, but I performed this test anyway, and am replying now with result:
* As mentioned above, the bug still occurs.
> I just checked our server logs. It appears you're using FireFox 1.5. Is that correct?
It might have been back then; I'm now using what I hope is the latest and greatest: Firefox 1.5.0.1
> Can you clear any support.sourcegear.com cookies from FireFox's Cookie Manager and try again. I want to know if that solves the forum's issue.
All my sourcegear cookies expire at end of session, but I performed this test anyway, and am replying now with result:
* As mentioned above, the bug still occurs.
> Are you logged in when responding to posts?
No, I just push the Reply button.
Maybe this is the entire culprit. I'm used to forums where the reply button works and forwards the users through login and on to the reply--in fact I'm so used to that, that I assumed it worked that way here without even noticing my assumption.
Maybe in this forum reply doesn't work unless you login as a separate step, and I'm spoiled by forums that handle reply & login together?
No, I just push the Reply button.
Maybe this is the entire culprit. I'm used to forums where the reply button works and forwards the users through login and on to the reply--in fact I'm so used to that, that I assumed it worked that way here without even noticing my assumption.
Maybe in this forum reply doesn't work unless you login as a separate step, and I'm spoiled by forums that handle reply & login together?
Test logging in first
Come to site
Browse to Support forum
Browse to thread
http://support.sourcegear.com/viewtopic ... 2728cef192
Instead of hitting Reply directly, I hit login, then login
Apparently it forgets where I was, as now it's lost the thread and sent me back to the forum list:
http://support.sourcegear.com/index.php ... 2728cef192
Browse to Support forum
Browse to thread
Push Reply
* Now it works (no error)
Browse to Support forum
Browse to thread
http://support.sourcegear.com/viewtopic ... 2728cef192
Instead of hitting Reply directly, I hit login, then login
Apparently it forgets where I was, as now it's lost the thread and sent me back to the forum list:
http://support.sourcegear.com/index.php ... 2728cef192
Browse to Support forum
Browse to thread
Push Reply
* Now it works (no error)
Back to thread actual topic.
Maybe this & another issue post are related:
Often running SourceGear Vault client temporarily frozen
http://support.sourcegear.com/viewtopic ... 57ef582124
Windows Offline Files
http://support.sourcegear.com/viewtopic ... 57ef582124
However, a quick check of Tools/Vault Options/Local Files/Cache/Backup Locations/In Custom Folder
shows me that -- I think -- my relevant directory is local.
On the same screen, Store Working Folder State/Baseline Files is set to Client Cache Folder.
Maybe this & another issue post are related:
Often running SourceGear Vault client temporarily frozen
http://support.sourcegear.com/viewtopic ... 57ef582124
Windows Offline Files
http://support.sourcegear.com/viewtopic ... 57ef582124
However, a quick check of Tools/Vault Options/Local Files/Cache/Backup Locations/In Custom Folder
shows me that -- I think -- my relevant directory is local.
On the same screen, Store Working Folder State/Baseline Files is set to Client Cache Folder.
This is definitely some kind of 2.0 framework bug/interaction. We have finally reproduced it in house (the GUI client using 2.0 framework and put in the background for a half hour or so will usually reproduce it). We are looking into the cause.
The workaround for now is to use the 1.1 framwork when using the GUI client.
The workaround for now is to use the 1.1 framwork when using the GUI client.