VS2008 crashes with SOS 5 each time connection is lost

[guillaume]

Hi,

In VS2008, With SOS 4, when the connection to the server was lost (renewal of dynamic IP address, network problems,...), boxes used to appear, saying something like "the connection to the server is lost". When the connection was OK again, to be able to go on working, I just needed to close those boxes and to click OK for the "do you want to reconnect to the server ?" box that came as soon as I did something that required SOS client to connect to the server.

With SOS 5, when internet connection is down, as soon as the SOS client needs connection to SOS server (almost immediately), VS2008 just crashes (and restarts), discarding any pending changes in code or IDE options. Even if I do not check "Perform background status updates"

Is there something to do ?

Ouput status messages is "through the IDE". Does it matter ?

Guillaume

[Beth]

Are you using SOS 5.0.0 or 5.0.1?

I can't reproduce the scenario and do receive a pop-up window offering to reconnect.

Could you look for your SOS client log at %TEMP%\.SOS\sosidelog.txt? What error does that log show?

[guillaume]

Hi,
I am using SOS 5.0.1

My %TEMP%\.SOS\sosidelog.txt shows

Code: Select all

[04/01/2010 09:43:11]   ### Starting SourceOffSite IDE Client ###
[04/01/2010 09:56:28]   CSOSBaseSocket::OnClose (nErrorCode = 10053)
[04/01/2010 09:56:48]   ### Starting SourceOffSite IDE Client ###

My event viewer log shows:

Code: Select all

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
	<System>
		<Provider Name="Application Error" />
		<EventID Qualifiers="0">1000</EventID>
		<Level>2</Level>
		<Task>100</Task>
		<Keywords>0x80000000000000</Keywords>
		<TimeCreated SystemTime="2010-01-04T08:56:28.000Z" />
		<EventRecordID>18364</EventRecordID>
		<Channel>Application</Channel>
		<Computer>xxxxxx</Computer>
		<Security />
	</System>
	<EventData>
		<Data>devenv.exe</Data>
		<Data>9.0.30729.1</Data>
		<Data>488f2b50</Data>
		<Data>ntdll.dll</Data>
		<Data>6.0.6002.18005</Data>
		<Data>49e03821</Data>
		<Data>c0000005</Data>
		<Data>0003e13d</Data>
	</EventData>
</Event>

Regards,
Guillaume

[Beth]

Could I have you find the following key in your registry, HKLM\Software\SourceCodeControlProvider -> ProviderRegKey? If your OS is a 64-bit OS, then you need to instead look for HKLM\Software\Wow6432Node\SourceCodeControlProvider -> ProviderRegKey. Go to the path listed in the ProviderRegKey and find a file there called SosScc.dll. Right-click that file, select properties, and go to the version tab. Which version is listed there?

[guillaume]

Hi,

file and product version for SosScc.dll is 5.0.1.242.

Regards,
Guillaume

[guillaume]

Hi,

I have been able to narrow the search around this problem:
- if "Send keep alive signal every" is checked, the IDE always crashes with VS2008, or may hang (but not always) with VS2005, as soon as it tries to send the alive signal.
- if I uncheck "Send keep alive signal every", the IDE is no longer crashing. Source control provider just gets disabled (with both VS2005 and VS2008), as soon as a call is made to the server:

Code: Select all

---- Operation started at time 14:30:59 ----
Retrieving File List: $/xxx/xxx/xxx
** The network connection to the server was closed. **
Your source control plug-in caused an exception or reported a fatal error.
Source control integration will be disabled until Microsoft Visual Studio is restarted or you change your source control plug-in selection.

With SOS 4, the plug in did not crash and it was possible to reconnect to the server as soon as the connection was up again, and go on working.
With SOS 5.0.1, even if I partially found a way around the crash problem and I do no longer lose unsaved changes, I need to restart the IDE manually to be able to work again with source control integration, what is still anoying enough.

Regards,
Guillaume

[jclausius]

guillaume,

Thanks for the report. It definitely narrows things down. I'm assuming everything still works correctly when the network connection remains up?

[Jared Sullivan]

I changed my port from 8080 to 21, not subject to 10053.

[jclausius]

OK. This will be fixed (no crashing) in the upcoming release, although if changing ports allows the connection to remain open that would result in a better solution as the IDE client will ask you to log in each and every time for a broken socket association.

[Jared Sullivan]

Hi,

Thanks for fixing the crash. My problem was I changed my Windows 7 from Power Mode to Balanced Power Plan and the Sleep property did not follow.

Can you guys add more logging to server.

"Server sleeping.."
"Server waking.."

Error 10053 is low level a TCP error

[jclausius]

Jared,

Where is the server located in relation to your client? Same machine?

Also, what is going to sleep here? Client? Server? Both?

[Jared Sullivan]

I have a Windows7 Machine 7KMs away that hosts SOS501 service, and the OS was either sleeping or trying to sleep with services. You may want to close the connection as well as logging "Server sleeping".

I suspect throwing the server into sleep mode is the same as a "20 minute" power save sleep. I also suspect if your server has a device(like my Logitech USB mouse\keyboard) that it may not going into a full sleep, and behavoiur again will change.

http://www.vbforums.com/showthread.php?t=502073

(6th thread --service freindly code.)

[jclausius]

For right now, I wouldn't recommend having a Server going to sleep. However, I'll log a feature request regarding the behavior.

Thanks for the feedback.

[scottbutler]

Hi,

I am having the same issue. Quite annoying. The connection to the server is lost almost immediately. When I then double click on a file in the pending checkins window to see the differences, I get an error message that says the source control provider crashed and will be disabled. VS then hangs.

Environment: Windows Vista Ultimate 32 bit, VS 2008, Source Offsite 5.0.1.242, SOS server is on the same network on a Windows 2003 Server 32 bit

Please help.

Thanks,

Scott

[jclausius]

Scott,

Help is on the way. The release should be ready sometime the next week (last week of March, 2010).

If you cannot wait and would like to try a pre-release, please mail sosbeta at sourcegear dot com, and we'll see where we need to go from here.