Running MacOS 10.14.5, SourceTree 3.2 (224)
I just started using BitBucket pipelines. SourceTree started popping up build success/failure messages, and my Mac's fan started to spin up dramatically. I noticed SourceTree was suddenly 'Using Significant Energy.'
I've been using SourceTree without issue for years, and this suddenly started, literally the moment I kicked off my first Pipelines build. Very weird. Disabling SourceTree notifications doesn't help, nor does killing and restarting SourceTree.
After some testing, it appears that while a BitBucket Pipeline is executing, Sourcetree starts using a ton of CPU time. As soon as the build is done, it drops back down to load CPU usage. Pretty weird.
Hi @Jason Machacek,
We are aware of some architectural limitations around the Pipelines feature that cause the CPU spike you noticed. There are plans to address this in a future update. Thank you for your patience and feedback!
Principal Developer, Sourcetree