Uploaded image for project: 'Sourcetree For Mac'
  1. Sourcetree For Mac
  2. SRCTREE-5762

App crashes on startup

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 2.7.5
    • 2.7.4
    • Git
    • None
    • Severity 2 - Major

      Startup fails with an immediate crash.

        1. image-2018-06-05-14-00-38-672.png
          image-2018-06-05-14-00-38-672.png
          27 kB

            [SRCTREE-5762] App crashes on startup

            Keith Reynolds added a comment -

            confirmed fix from v 2.7.5a.

            Thank you!

            Keith Reynolds added a comment - confirmed fix from v 2.7.5a. Thank you!

            Brooke Noble added a comment -

            I believe this is a duplicate of SRCTREE-5769which is now resolved. Not sure why no one from Atlassian is linking these.

            Brooke Noble added a comment - I believe this is a duplicate of  SRCTREE-5769 which is now resolved. Not sure why no one from Atlassian is linking these.

            Darren Warner added a comment -

            No impact after removing ImageCache/. I don't see any new images in this directory after launching, but the directory was re-created.

             

            Darren Warner added a comment - No impact after removing ImageCache/. I don't see any new images in this directory after launching, but the directory was re-created.  

            Manju added a comment -

            Can you remove the image cache folder under the  ~/Library/Application\ Support/SourceTree/ and see if it helps. The crash logs indicate something going wrong with reading the image cache for the repo avatars. 

            Manju added a comment - Can you remove the image cache folder under the  ~/Library/Application\ Support/SourceTree/ and see if it helps. The crash logs indicate something going wrong with reading the image cache for the repo avatars. 

            Darren Warner added a comment -

            I removed  /Library/Application\ Support/Sourcetree/, then launched SourceTree and it was Ok.

            Then I scanned my project directory. The import worked, but SourceTree now crashes part way through checking repo status. So it seems to be something in one of my repositories that's triggering this crash.

             

            Darren Warner added a comment - I removed  /Library/Application\ Support/Sourcetree/, then launched SourceTree and it was Ok. Then I scanned my project directory. The import worked, but SourceTree now crashes part way through checking repo status. So it seems to be something in one of my repositories that's triggering this crash.  

            Jurn Overmars added a comment - - edited

            For me it has been solved to delete the directory `/Library/Application\ Support/Sourcetree/` and because this is not a solution i restored a backup from yesterday (Timemachine) and this worked as well. So it looks like the files in this directory are corrupt or the permissions are changed. 

             

             I also updated the Sourcetree but this was not a solution either.

            Crash Report:
            https://gist.github.com/xleeuwx/79179c4afa08d092a0d60af518f8fa35

            If needed i have more where that came from. 

             

            FYI: thinks that i notice what that i needed to accept the privacy policy from Gitlab and i have Gitlab / Github / Bitbucket accounts in my Sourcetree. The current working project that was open a Github project. 

            So i accepted the policy and moved on but i am not sure if this is the cause of the problem but i have not updated the Sourcetree in a few weeks. So the problem occurred this morning 06-06-2018 at ~01:00 GMT+2 i am not sure if this all have something to do with the issue but maybe it can help

            Jurn Overmars added a comment - - edited For me it has been solved to delete the directory `/Library/Application\ Support/Sourcetree/` and because this is not a solution i restored a backup from yesterday (Timemachine) and this worked as well. So it looks like the files in this directory are corrupt or the permissions are changed.     I also updated the Sourcetree but this was not a solution either. Crash Report: https://gist.github.com/xleeuwx/79179c4afa08d092a0d60af518f8fa35 If needed i have more where that came from.    FYI: thinks that i notice what that i needed to accept the privacy policy from Gitlab and i have Gitlab / Github / Bitbucket accounts in my Sourcetree. The current working project that was open a Github project.  So i accepted the policy and moved on but i am not sure if this is the cause of the problem but i have not updated the Sourcetree in a few weeks. So the problem occurred this morning 06-06-2018 at ~01:00 GMT+2 i am not sure if this all have something to do with the issue but maybe it can help

            Jamy Cuijpers added a comment -

            Same issue in version 2.7 (144):

            https://gist.github.com/jamyc/6c0819e10e349b9643cac845e6338165

             

            Removed Sourcetree and installed 2.7.4 (175) and still crashes:

            https://gist.github.com/jamyc/bb2a64de990e9f794da459d43a74d863

            Jamy Cuijpers added a comment - Same issue in version 2.7 (144): https://gist.github.com/jamyc/6c0819e10e349b9643cac845e6338165   Removed Sourcetree and installed 2.7.4 (175) and still crashes: https://gist.github.com/jamyc/bb2a64de990e9f794da459d43a74d863

            Brooke Noble added a comment -

            Same problem, here's my crash log

            https://gist.github.com/bdn75/d74361a8a5527958601b600a612eac9f

            Brooke Noble added a comment - Same problem, here's my crash log https://gist.github.com/bdn75/d74361a8a5527958601b600a612eac9f

            Darren Warner added a comment -

            https://gist.github.com/dazwin/0d3e5dee95532979fac99190b8ee464c

            Darren Warner added a comment - https://gist.github.com/dazwin/0d3e5dee95532979fac99190b8ee464c

            Manju added a comment -

            I'm afraid not, some of the information to symbolicate the crashes are available in the actual .crash file. Would you be able to share it by some other means. And, I'll work with the team here to get the permissions for attachments fixed so that you don't see this problem next time around. Thanks!

            Manju added a comment - I'm afraid not, some of the information to symbolicate the crashes are available in the actual .crash file. Would you be able to share it by some other means. And, I'll work with the team here to get the permissions for attachments fixed so that you don't see this problem next time around. Thanks!

              Unassigned Unassigned
              4f4aaecdf797 Keith Reynolds
              Affected customers:
              3 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: