Uploaded image for project: 'Sourcetree for Windows'
  1. Sourcetree for Windows
  2. SRCTREEWIN-11400

After update to 2899, application fails to launch. Error log in description.

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • None
    • 3.1.0-beta-2899
    • General
    • Windows 10 Pro Insiders Edition (latest build from MS)

    • Severity 1 - Critical

      After an update either from within ST or from the installer (tried both ways) the application becomes unable to launch.  I blow out the new 2899 folder and then I am able to launch the older version.  I have searched windows event logs, only thing I find is in the sourcetree.log:

      ERROR [2019-03-04 09:42:06,090] [1] [SourceTree.App] [Log] - Failed to start
      System.NullReferenceException: Object reference not set to an instance of an object.
      at SourceTree.AppRoot.DoWindowStartupTasks()
      at SourceTree.ViewModel.MainWindowViewModel.DoStartupTasks()
      at SourceTree.ViewModel.MainWindowViewModel..ctor(IRepositoryTabContainerViewModel repositoryTabContainerViewModel, ICustomActionsManager customActionsManager, IRepositoryManager repositoryManager, IAnalyticsDataManager analyticsDataManager, ITraceManager traceManager, IDispatcher dispatcher, IAccountManager accountManager, IFailureHandler failureHandler, IDvcsManager dvcsManager, IConfigurationManager configurationManager, IInstanceManager instanceManager, ISchedulerManager schedulerManager, IWebManager webManager, IRepositoryMonitorManager repositoryMonitorManager, ISshKeyManager sshKeyManager, INotificationsManager notificationsManager, IPreferencesManager preferencesManager, IRepoProcessFactory repoProcessFactory, IBookmarkManager bookmarkManager)
      at SourceTree.MainWindow..ctor(IRepositoryTabContainerViewModel repositoryTabContainerViewModel, ICustomActionsManager customActionsManager, IRepositoryManager repositoryManager, IAnalyticsDataManager analyticsDataManager, ITraceManager traceManager, IDispatcher dispatcher, IAccountManager accountManager, IFailureHandler failureHandler, IDvcsManager dvcsManager, IConfigurationManager configurationManager, IInstanceManager instanceManager, ISchedulerManager schedulerManager, IWebManager webManager, IRepositoryMonitorManager repositoryMonitorManager, IApplicationManager applicationManager, ISshKeyManager sshKeyManager, INotificationsManager notificationsManager, IBookmarkManager bookmarkManager, IPreferencesManager preferencesManager, IRepoProcessFactory repoProcessFactory)
      at SourceTree.AppRoot.<OnStartup>d__31.MoveNext()
      — End of stack trace from previous location where exception was thrown —
      at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
      at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
      at SourceTree.App.<OnStartup>d__4.MoveNext()
      DEBUG [2019-03-04 09:42:06,121] [20] [SourceTree.Instances.SingleInstance] [Log] - SingleInstance pipe connection received
      DEBUG [2019-03-04 09:42:06,121] [20] [SourceTree.Instances.SingleInstance] [Log] - SingleInstance waiting for connection: iar is not null
      DEBUG [2019-03-04 09:42:06,121] [1] [SourceTree.Configuration.DefaultConfigurationManager] [Log] - Saved settings
      DEBUG [2019-03-04 09:42:06,136] [1] [SourceTree.AppRoot] [Log] - Unregister crash event handlers for [SourceTree.Analytics.Crash.BugSplat.CrashAnalyticsService]
      DEBUG [2019-03-04 09:42:06,136] [1] [Sourcetree.Analytics.Emau.EMauSubmissionService] [Log] - Stop submission

            [SRCTREEWIN-11400] After update to 2899, application fails to launch. Error log in description.

            Please update to the latest version of Sourcetree. We have already fixed this issue.

            Mukesh Kumar added a comment - Please update to the latest version of Sourcetree. We have already fixed this issue.

            minnsey added a comment -

            Sorry

            user.config will be in a %localappdata%/Atlassian/Sourcetree.exe_url_{hash}/{version} folder
            .gitconfig will be in your HOME folder

            minnsey added a comment - Sorry user.config will be in a %localappdata%/Atlassian/Sourcetree.exe_url_{hash}/{version} folder .gitconfig will be in your HOME folder

            I've searched SourceTreebeta and SourceTree-Settings folders and have not found the files (user.config or any git.config).  Am I looking in the right place?  I did a global search but no luck there either.

             

            Jay Beeckman added a comment - I've searched SourceTreebeta and SourceTree-Settings folders and have not found the files (user.config or any git.config).  Am I looking in the right place?  I did a global search but no luck there either.  

            minnsey added a comment -

            Hi thanks for that I think that will help a lot.

            Would you be able to provide the user.config, please check for any sensitive information, and also the diff and merge tool settings from Git config?

            Thanks

            minnsey added a comment - Hi thanks for that I think that will help a lot. Would you be able to provide the user.config, please check for any sensitive information, and also the diff and merge tool settings from Git config? Thanks

            Jay Beeckman added a comment - - edited

            Still same behavior, but it now logs a little more information:

            ERROR [2019-03-11 09:58:48,622] [1] [SourceTree.App] [Log] - Failed to start
            System.NullReferenceException: Object reference not set to an instance of an object.
            at SourceTree.AppRoot.ToolConfigurationIsValid(IDiffMergeTool tool)
            at SourceTree.AppRoot.DoWindowStartupTasks()
            at SourceTree.ViewModel.MainWindowViewModel.DoStartupTasks()

             

            I compared the config files and the changes did not see any changes to the diff settings.  I'm still willing to help however I can...

            Jay Beeckman added a comment - - edited Still same behavior, but it now logs a little more information: ERROR [2019-03-11 09:58:48,622] [1] [SourceTree.App] [Log] - Failed to start System.NullReferenceException: Object reference not set to an instance of an object. at SourceTree.AppRoot.ToolConfigurationIsValid(IDiffMergeTool tool) at SourceTree.AppRoot.DoWindowStartupTasks() at SourceTree.ViewModel.MainWindowViewModel.DoStartupTasks()   I compared the config files and the changes did not see any changes to the diff settings.  I'm still willing to help however I can...

            I understand on the closed source, was just trying to help....   I find that issues that I usually have, are usually issues at some point for others   I like to live on the edge and am pretty good at at least identifying problems.  Is there a way to turn on more logging?  Also, if it's in a plugin initialization, can you wrap the inner loop in a try catch and log errors?  Since it's on startup (and I am only guessing) there should not be much performance hit...   But a null reference exception is kinda ick to try to figure out with no source.  I will certainly try the new beta as soon as it is released...

            Jay Beeckman added a comment - I understand on the closed source, was just trying to help....   I find that issues that I usually have, are usually issues at some point for others   I like to live on the edge and am pretty good at at least identifying problems.  Is there a way to turn on more logging?  Also, if it's in a plugin initialization, can you wrap the inner loop in a try catch and log errors?  Since it's on startup (and I am only guessing) there should not be much performance hit...   But a null reference exception is kinda ick to try to figure out with no source.  I will certainly try the new beta as soon as it is released...

            minnsey added a comment -

            Sorry the source is closed.

            I'm not sure what to suggest, to be honest.

            We are about to release a new beta, I'd be interested to see if there is any difference with it.

            minnsey added a comment - Sorry the source is closed. I'm not sure what to suggest, to be honest. We are about to release a new beta, I'd be interested to see if there is any difference with it.

            I removed the entire install and all settings and used a fresh install vs the update from within the app and had the same result.  I fall back to the 2660 beta and it works again.  I normally suspect my Windows Insider builds, which are weekly...  But in this case, I install the 2899 and it breaks, fall back and it works, so I don't think it's that.  Is the source code available anywhere?  I could debug and find the exact cause.  The splash screen launches, then everything shuts down.

            Jay Beeckman added a comment - I removed the entire install and all settings and used a fresh install vs the update from within the app and had the same result.  I fall back to the 2660 beta and it works again.  I normally suspect my Windows Insider builds, which are weekly...  But in this case, I install the 2899 and it breaks, fall back and it works, so I don't think it's that.  Is the source code available anywhere?  I could debug and find the exact cause.  The splash screen launches, then everything shuts down.

            minnsey added a comment -

            At a guess it looks like some part of the component/plugins is failing to load.

            Unfortunately I can't tell which from the logs. This is the only report we've seen of this. If you blow away all of the Sourcetree install and configuration and do a completely clean beta install does it make an improvement?

            minnsey added a comment - At a guess it looks like some part of the component/plugins is failing to load. Unfortunately I can't tell which from the logs. This is the only report we've seen of this. If you blow away all of the Sourcetree install and configuration and do a completely clean beta install does it make an improvement?

              698877135425 Mukesh Kumar
              e8a23b31af57 Jay Beeckman
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: