• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • None
    • 4.2.2
    • Bitbucket
    • None
    • Severity 2 - Major

      On an M1 MacBook Air the system is reporting that Sourcetree uses and significant amount of battery. After opening Sourcetree for a short period of time and then quitting the application it still uses a significant amount of battery and noticeably reduce the battery charge. Activity monitor reports multiple instances of Sourcetree Login running and I am unable to force quit this process. The only way to resolve this is to completely restart the MacBook. Next time I open Sourcetree this issue will come back.

            [SRCTREE-8020] Sourcetree uses a significant amount of battery.

            The fix for this issue is available in Sourcetree 4.2.4.
            You could upgrade your Sourcetree via "Check For Updates" feature or directly download it from official website.
            Thanks.

            Raman Sidarakin (Inactive) added a comment - The fix for this issue is available in Sourcetree 4.2.4. You could upgrade your Sourcetree via "Check For Updates" feature or directly download it from official website. Thanks.

            Hi, d27eae982eb0
            Thanks for your answers.
            Now from your answers I see that your issue is related to SSH repository and SSH configuration. I'll create internal ticket for analysing this issue and we will take a look at this issue in order of priorities.
            Even it not reproducible for you at this moment of time, it looks like there is some issue and other users may be affected too.

            Thanks!

            Raman Sidarakin (Inactive) added a comment - Hi, d27eae982eb0 Thanks for your answers. Now from your answers I see that your issue is related to SSH repository and SSH configuration. I'll create internal ticket for analysing this issue and we will take a look at this issue in order of priorities. Even it not reproducible for you at this moment of time, it looks like there is some issue and other users may be affected too. Thanks!

            Hi @Raman, thanks for the response.

            After either a recent macOS update or Sourcetree update I am no longer able reproduce the issue. If it helps though, I will try and answer your questions:

            1. Sourcetree Version: 4.2.2 (I do not know what version I was on when the issue happened.)
            2. macOS: 13.3 (previously, when the issue was happening I was on 13.2)
            3. Embedded Git
            4. https
            5. OpenSSH_9.0p1, LibreSSL 3.3.6
            1. I can no longer reproduce the issue
            2. I noticed my remote repo was configured for SSH and was failing to connect. I switch the protocol to to https. After switch I was able to connect to the remote repo but after that is when I noticed the power usage issue.
            3. git pull command fails authentication when I try to log in with my Bitbucket credentials.

            On your note about killing the SourceTreeLogin processes. I actually tried that but either the process couldn't be killed or the process were respawning. When I tried to kill the processes (from the screen shot you can see multiple instances we running) some would exit but then immediately return. The only resolution I could find is completely rebooting my MacBook.

             

            mkulich-aptos-com added a comment - Hi @Raman, thanks for the response. After either a recent macOS update or Sourcetree update I am no longer able reproduce the issue. If it helps though, I will try and answer your questions: Sourcetree Version: 4.2.2 (I do not know what version I was on when the issue happened.) macOS: 13.3 (previously, when the issue was happening I was on 13.2) Embedded Git https OpenSSH_9.0p1, LibreSSL 3.3.6 I can no longer reproduce the issue I noticed my remote repo was configured for SSH and was failing to connect. I switch the protocol to to https. After switch I was able to connect to the remote repo but after that is when I noticed the power usage issue. git pull command fails authentication when I try to log in with my Bitbucket credentials. On your note about killing the SourceTreeLogin processes. I actually tried that but either the process couldn't be killed or the process were respawning. When I tried to kill the processes (from the screen shot you can see multiple instances we running) some would exit but then immediately return. The only resolution I could find is completely rebooting my MacBook.  

            Hi, d27eae982eb0
            Thanks for contacting us and reporting this issue.

            Unfortunately we could not reproduce the same behaviour and we need additional information from your side to understand what is going on.

            Basically, the "SourceTreeLogin" process is a credential helper that is responsible for handling prompts from git. It looks like due to some reason it hangs on your machine and Sourcetree keeps spawning new "SourceTreeLogin" processes. It will be great, if you provide answers to these questions:
            1. Could you please confirm you are using Sourcetree 4.2.2?
            2. Which version of macOS is currently installed on your machine? ( -> About This Mac)
            3. Are you using "Embedded Git" or "System Git"? To check this please open Sourcetree settings and switch to "Git" tab. Observe "Git Version" panel.
            4. Could you please tell me which protocol you are using to work with repos: ssh, https or both?
            5. Could you please tell me version of ssh agent on your machine? (Open Terminal and type "ssh -V".)
            6. It looks like we need to take a look at your logs from Sourcetree.
            To enable debug logging you need to do the following: Go to Sourcetree -> Settings -> Advanced. Check "Show debug menu".
            Then go to main menu in status bar and go to "Debug" -> Log Level -> Select "Debug".
            Relaunch Sourcetree and try to reproduce your issue.
            After issue is reproduced and Sourcetree was active about 3-5 minutes you need to open Sourcetree Main menu -> "Debug" -> Open Logs Folder.
            Then share this logs with us and we will take a look for possible uncommon or abnormal entries which could point to the reason of this issue.
            7. Maybe you remember when this issue occurred first time and you could link it with some actions related to configuration, e.t.c. Or it first time when you are using Sourcetree?
            8. Could you please check if you could work with repositories that you've added to Sourcetree using Terminal? Could you please check simple "git pull" or some other command that invokes some interaction with repository remote? It may be helpful for diagnosing this.

            Note:
            You could finish all active "SourceTreeLogin" processes using terminal. Just type "killall SourceTreeLogin". It's not a fix, it's alternative to restarting your machine.

            Looking forward for your reply and thanks in advance for your answers.

            Raman Sidarakin (Inactive) added a comment - Hi, d27eae982eb0 Thanks for contacting us and reporting this issue. Unfortunately we could not reproduce the same behaviour and we need additional information from your side to understand what is going on. Basically, the "SourceTreeLogin" process is a credential helper that is responsible for handling prompts from git. It looks like due to some reason it hangs on your machine and Sourcetree keeps spawning new "SourceTreeLogin" processes. It will be great, if you provide answers to these questions: 1. Could you please confirm you are using Sourcetree 4.2.2? 2. Which version of macOS is currently installed on your machine? ( -> About This Mac) 3. Are you using "Embedded Git" or "System Git"? To check this please open Sourcetree settings and switch to "Git" tab. Observe "Git Version" panel. 4. Could you please tell me which protocol you are using to work with repos: ssh, https or both? 5. Could you please tell me version of ssh agent on your machine? (Open Terminal and type "ssh -V".) 6. It looks like we need to take a look at your logs from Sourcetree. To enable debug logging you need to do the following: Go to Sourcetree -> Settings -> Advanced. Check "Show debug menu". Then go to main menu in status bar and go to "Debug" -> Log Level -> Select "Debug". Relaunch Sourcetree and try to reproduce your issue. After issue is reproduced and Sourcetree was active about 3-5 minutes you need to open Sourcetree Main menu -> "Debug" -> Open Logs Folder. Then share this logs with us and we will take a look for possible uncommon or abnormal entries which could point to the reason of this issue. 7. Maybe you remember when this issue occurred first time and you could link it with some actions related to configuration, e.t.c. Or it first time when you are using Sourcetree? 8. Could you please check if you could work with repositories that you've added to Sourcetree using Terminal? Could you please check simple "git pull" or some other command that invokes some interaction with repository remote? It may be helpful for diagnosing this. Note: You could finish all active "SourceTreeLogin" processes using terminal. Just type "killall SourceTreeLogin". It's not a fix, it's alternative to restarting your machine. Looking forward for your reply and thanks in advance for your answers.

              Unassigned Unassigned
              d27eae982eb0 mkulich-aptos-com
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: