Sourcetree hangs on start-up after update

[Deleted user]

Hi,

Sourcetree hangs on start-up after the latest update.

In sourcetree.log there is a repeated error, maybe it's related (i assume it's an infinite loop):

Any ideas/suggestions?

ERROR [2019-11-08 17:58:15,266] [21] [Sourcetree.Analytics.Emau.EMauSubmissionService] [Log] - POST MAU submission FAILED
System.IO.FileLoadException: Could not load file or assembly 'TimeZoneConverter, Version=2.3.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'TimeZoneConverter, Version=2.3.0.0, Culture=neutral, PublicKeyToken=null'
at Atlassian.AnalyticsService.Client.Converters.IanaTimezoneConverter.WriteJson(JsonWriter writer, Object value, JsonSerializer serializer)
at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeConvertable(JsonWriter writer, JsonConverter converter, Object value, JsonContract contract, JsonContainerContract collectionContract, JsonProperty containerProperty)
at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)
at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.SerializeObject(JsonWriter writer, Object value, JsonObjectContract contract, JsonProperty member, JsonContainerContract collectionContract, JsonProperty containerProperty)
at Newtonsoft.Json.Serialization.JsonSerializerInternalWriter.Serialize(JsonWriter jsonWriter, Object value, Type objectType)
at Newtonsoft.Json.JsonSerializer.SerializeInternal(JsonWriter jsonWriter, Object value, Type objectType)
at Newtonsoft.Json.JsonConvert.SerializeObjectInternal(Object value, Type type, JsonSerializer jsonSerializer)
at Sourcetree.Analytics.Emau.EMauSubmissionService.<SubmitBatch>d__62.MoveNext()

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

[Jhonathan Correa]

(deleted)

[Ilia Burakov]

I have the same problem on SourceTree.exe, version: 3.4.9.0.

There are always two messages in the log:

1)

Application: SourceTree.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at SourceTree.Analytics.Emau.EMauSubmissionService+<SubmitBatch>d__40.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at System.Runtime.CompilerServices.TaskAwaiter`1[[System.Boolean, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].GetResult()
at SourceTree.Analytics.Emau.EMauSubmissionService+<Submit>d__39.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
at System.Runtime.CompilerServices.TaskAwaiter`1[[System.Boolean, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].GetResult()
at SourceTree.Analytics.Emau.EMauSubmissionService+<SubmissionTimer_Elapsed>d__37.MoveNext()
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()

2)

Faulting application name: SourceTree.exe, version: 3.4.9.0, time stamp: 0x62875751
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1826, time stamp: 0x299341e8
Exception code: 0xe0434352
Fault offset: 0x0000000000034fd9
Faulting process id: 0x5e80
Faulting application start time: 0x01d89b3dfdfeefdc
Faulting application path: C:\Users\Unnamed\AppData\Local\SourceTree\app-3.4.9\SourceTree.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: ee902967-763d-4b93-b2c6-4a1360566edd
Faulting package full name:
Faulting package-relative application ID:

[Jhonathan Correa]

I had this exact same problem and the cause was the proxy/firewall blocking a post to "https://as.atlassian.com/api/v1/import".

[Christopher Beck]

I get the same error trying to open a repo.

[Carlos Carvalho]

Me too with the version downloaded from AutoUpdate. But with 3.2.6 i didn't have problem at all.

At the sourcetree main site, the download link point to 3.2.6, not to 3.3.4 from auto update notification.

I use Windows and have the Kaspersky antivirus.

I'm from Brazil and have been experiencing many issues in other programs because the extinsion of the summer time in Brazil.

[Matthew Evjy]

I am having the same issue with version SourceTree Version 3.3.6.

[Ryan Halley]

Me too. 3.3.6. Hung yesterday evening after hours of use, and now today it does it immediately after loading.

[Ryan Halley]

I tried downgrading to the each of the previous 3 versions and that just made matters worse, giving me a log error about no respositories found, with a hang.

I had to uninstall, then remove AppData\Local\Atlassian and AppData\Local\Sourcetree - that allowed me to do a fresh install. During the install, at the end, I got asked if I had an ssh key to use - if I said yes, nothing then happened. I had to instead choose No, and then the app loaded - I then saw that there was an update available for 3.3.7, which I'm now using. If I go into Pageant, and click 'Add', it hangs - this may well have been the source of the issues all along.

Update: Yes, it turned out that Pageant was trying to load my keys from a NAS, and the NAS connection was down. So, SourceTree completely defers to Pageant and waits indefinitely, without any explanation as to what is going on - can I suggest a timeout after 20seconds, and then a message saying, "There was a problem whilst trying to retrieve your SSH key", and then you have complete access to ST again. Would have saved me a couple of hours.

[Carlos Carvalho]

I didn't try do upgrade yet, I'm still in version 3.2.6. My guess is that the error occur because summertime (daylight saving time) in my country (Brazil). This year we doesn't have summertime and because that several apps are showing wrong time (Google Maps, Skype...). For those other apps, I change my timezone to a local in Brazil that doesn't have summertime(daylight saving time) in 2018.