Vault client 5.0.2 crashing

[stevek2]

One of our developers is seeing pretty consistent crashes with the 5.0.2 VaultGuiClient. I have attached a log file that was running at the time of the crash. He isn't really doing anything when Vault crashes, he's just got it minimized and after a while it crashes while he's doing other things. In this specific trace, it was logging stuff all weekend and it crashed this morning.

[lbauer]

Is the last line in the log when the crash happened? If so, it looks like it crashed while scanning folders.

Was the user using VSS or CVS mode? Could you send me a copy of the Vault Server log for the corresponding timeframe? It's called sgvault.log and is in %windir%\temp\sgvault on the server machine. Send the log zipped up to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

[stevek2]

We're not sure if the crash happened at 9:59:07AM or not -- it was pretty close to this time, but we can't rule out that it crashed a few minutes after this last log entry (it had to be less than 10 minutes after because the client is doing an auto-refresh every 10 minutes, so at 10:09AM it would have begun a refresh). The 2nd-to-last line is 'Auto refresh finished', and the last line the 'exception while scanning for missing files', and these 2 lines end the auto-refresh entries which occur every 10 minutes.

Notice that the 'StatusSearchRestartNeededException' is happening each time -- the user had a search set up for 'missing' files and had forgotten he had that refreshing in the background. He's since turned that off, so we'll see if it's still crashing now.

The user was using CVS mode.

The server sgvault.log file does not show anything interesting -- it's apparently only logging Login/Logout requests, so that's all that's in the log for last few days.

When the crash happens, is it possible to get a coredump or something similar that we could send to you?

[lbauer]

A core dump wouldn't be too helpful, but you could check the Event Viewer on the client machine to see what was reported at the time of the crash. Also, if we're able to pinpoint the time of the crash in the client log, we can see what went on prior to that.

[stevek2]

The Event viewer isn't going to show anything interesting. A saved image of the working set of the VaultGuiClient at the time of the crash should be easily debuggable.

And I don't think you're understanding me about the time of the crash -- the last line of the log was the last event written by the client before it crashed. I was making the point that it didn't necessarily crash _while_ performing the activity associated with that last line.

So where do we go from here?

[lbauer]

I'd like to see a copy of the Vault server log for the same time period as the client log. there aren't any significant errors in the client log, but it could be if the client is losing its connection with the server, it could be causing it to crash.

It's called sgvault.log and is in %windir%\temp\sgvault on the server machine. You can post it here or end the log zipped up to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.