• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 1.8.2
    • 1.8.0.36401
    • None

      Almost every operation you do it just jumps on "File Status"

            [SRCTREEWIN-4197] Jumps on "File Status" very very very ... often

            jdforsythe928155827, you are right, but that is a totally different error.

            The issue solved here was about an automatic changing tab every 15 minutes, with no action needed.

            You found a NEW bug, you should report it.

            Benjamin Fernandez added a comment - jdforsythe928155827 , you are right, but that is a totally different error. The issue solved here was about an automatic changing tab every 15 minutes, with no action needed. You found a NEW bug, you should report it.

            This is definitely not fixed. Still present in 1.8.3.0.

            Related to https://jira.atlassian.com/browse/SRCTREEWIN-4197

            and others.

            Easy to reproduce. On a feature branch, double-click Master to switch branches, then quickly right-click the feature branch and choose "Merge [feature] to master". The context menu correctly reports the name of the branch you want to merge, but behind the scenes the highlight has moved to "File Status" - so you get an error that you can't merge "File Status". So cancel and merge again, it's fine. Then quickly right-click to delete the feature branch and again an error, cannot delete "File Status"... incredibly annoying. This was not present in the old ui.

            Jeremy Forsythe added a comment - This is definitely not fixed. Still present in 1.8.3.0. Related to https://jira.atlassian.com/browse/SRCTREEWIN-4197 and others. Easy to reproduce. On a feature branch, double-click Master to switch branches, then quickly right-click the feature branch and choose "Merge [feature] to master". The context menu correctly reports the name of the branch you want to merge, but behind the scenes the highlight has moved to "File Status" - so you get an error that you can't merge "File Status". So cancel and merge again, it's fine. Then quickly right-click to delete the feature branch and again an error, cannot delete "File Status"... incredibly annoying. This was not present in the old ui.

            Thank you guys. Cheers.

            Kilian Demeulemeester added a comment - Thank you guys. Cheers.

            dodonew added a comment -

            Thanks a lot! Hope update comes soon.

            dodonew added a comment - Thanks a lot! Hope update comes soon.

            Thanks! Looking forward to the update.

            nikolajskov added a comment - Thanks! Looking forward to the update.

            Thank you guys!

            Benjamin Fernandez added a comment - Thank you guys!

            Ben Wolf added a comment -

            Cool, thanks for the fast reply. Can't wait for the fix, it's very annoying. But it is good to see that you're very fast in reacting to user feedback.

            Ben Wolf added a comment - Cool, thanks for the fast reply. Can't wait for the fix, it's very annoying. But it is good to see that you're very fast in reacting to user feedback.

            minnsey added a comment -

            We are currently testing a release containing a fix for this. We will ensure we test this more thoroughly to avoid repeating the disruption you have all experienced. Apologies.

            The error is due to background refreshes of the Side bar information, which triggers a refresh of the sidebar display which in turn resets the selected tree node to the Working Copy entry, this in turn triggers the switch from the Log View to the File Status view.

            Apologies again.

            minnsey added a comment - We are currently testing a release containing a fix for this. We will ensure we test this more thoroughly to avoid repeating the disruption you have all experienced. Apologies. The error is due to background refreshes of the Side bar information, which triggers a refresh of the sidebar display which in turn resets the selected tree node to the Working Copy entry, this in turn triggers the switch from the Log View to the File Status view. Apologies again.

            Greg MacLellan added a comment - - edited

            Prior version: https://downloads.atlassian.com/software/sourcetree/windows/SourceTreeSetup_1.7.0.32509.exe (note 1.7.0.36739 doesn't seem to be published here).

            Note however, after running 1.8.1.0, 1.7.0 now crashes. I have even tried removing my %localappdata%\Atlassian\SourceTree, but it recreates it, crashes and in the log puts:

            ERROR [2016-02-17 09:55:19,932] [1] [SourceTree.Accounts.AccountManager] [.ctor] - Unable to load accounts
            System.UnauthorizedAccessException: Access to the path 'C:\Program Files (x86)\Atlassian\SourceTree\AppData\Local\Atlassian\SourceTree' is denied.
            ERROR [2016-02-17 09:55:20,097] [1] [SourceTree.AppRoot] [HandleCrash] - Fatal error
            System.NullReferenceException: Object reference not set to an instance of an object.
               at SourceTree.AppRoot.OnStartup(StartupEventArgs e) in C:\projects\bitbucket.org\atlassian\sourcetreewin-prod\AppRoot.cs:line 184
            ERROR [2016-02-17 09:55:20,275] [1] [SourceTree.AppRoot] [HandleCrash] - Fatal error
            System.NullReferenceException: Object reference not set to an instance of an object.
               at SourceTree.AppRoot.OnActivated(EventArgs e) in C:\projects\bitbucket.org\atlassian\sourcetreewin-prod\AppRoot.cs:line 158
            ERROR [2016-02-17 09:55:23,785] [1] [SourceTree.AppRoot] [HandleCrash] - Fatal error
            System.NullReferenceException: Object reference not set to an instance of an object.
               at SourceTree.AppRoot.OnDeactivated(EventArgs e) in C:\projects\bitbucket.org\atlassian\sourcetreewin-prod\AppRoot.cs:line 175
            [many more ignored]
            

            I just want to get my work done, this update has actually prevented me from using SourceTree entirely.

            Greg MacLellan added a comment - - edited Prior version: https://downloads.atlassian.com/software/sourcetree/windows/SourceTreeSetup_1.7.0.32509.exe (note 1.7.0.36739 doesn't seem to be published here). Note however, after running 1.8.1.0, 1.7.0 now crashes. I have even tried removing my %localappdata%\Atlassian\SourceTree , but it recreates it, crashes and in the log puts: ERROR [2016-02-17 09:55:19,932] [1] [SourceTree.Accounts.AccountManager] [.ctor] - Unable to load accounts System .UnauthorizedAccessException: Access to the path 'C:\Program Files (x86)\Atlassian\SourceTree\AppData\Local\Atlassian\SourceTree' is denied. ERROR [2016-02-17 09:55:20,097] [1] [SourceTree.AppRoot] [HandleCrash] - Fatal error System .NullReferenceException: Object reference not set to an instance of an object. at SourceTree.AppRoot.OnStartup(StartupEventArgs e) in C:\projects\bitbucket.org\atlassian\sourcetreewin-prod\AppRoot.cs:line 184 ERROR [2016-02-17 09:55:20,275] [1] [SourceTree.AppRoot] [HandleCrash] - Fatal error System .NullReferenceException: Object reference not set to an instance of an object. at SourceTree.AppRoot.OnActivated(EventArgs e) in C:\projects\bitbucket.org\atlassian\sourcetreewin-prod\AppRoot.cs:line 158 ERROR [2016-02-17 09:55:23,785] [1] [SourceTree.AppRoot] [HandleCrash] - Fatal error System .NullReferenceException: Object reference not set to an instance of an object. at SourceTree.AppRoot.OnDeactivated(EventArgs e) in C:\projects\bitbucket.org\atlassian\sourcetreewin-prod\AppRoot.cs:line 175 [many more ignored] I just want to get my work done, this update has actually prevented me from using SourceTree entirely.

            I have noticed this as well in 1.8.1.0. It happens with VisualStudio 2015, while VS itself is open (but not explicitly doing anything). If I close VisualStudio, it stops.

            For me this is a critical bug that makes this version of SourceTree fully unusable: I cannot at all use the log view while VisualStudio is open. Having to close my IDE every time I want to use log view is a complete non-starter.

            Greg MacLellan added a comment - I have noticed this as well in 1.8.1.0. It happens with VisualStudio 2015, while VS itself is open (but not explicitly doing anything). If I close VisualStudio, it stops. For me this is a critical bug that makes this version of SourceTree fully unusable: I cannot at all use the log view while VisualStudio is open. Having to close my IDE every time I want to use log view is a complete non-starter.

              mminns minnsey
              e9b2cc687617 Sotirca Mihai
              Affected customers:
              26 This affects my team
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: