Slow "activation time" about status-bar

[stramel]

I am hitting the same issue for Loading and Activation.

Loading:

Activation:

PC Specs:

• Intel® Core™ i7-4800MQ CPU @ 2.70GHz × 8
• 16 GB 1600Mhz DDR3
• Ubuntu 14.04 64-bit
• 3.13.0-54-generic

[harrislapiroff]

My machine is admittedly older, but this has consistently been taking more than 1s to activate, which makes Atom very slow to start for me.

2.4 GHz Intel Core 2 Duo
8 GB 1067 MHz DDR3
OS X 10.10.3

[entr]

Additional packages

├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]

Atom 1.0
Intel® Core™ i7-4712MQ CPU @ 2.30GHz
16 GB 1600Mhz DDR3
Linux Mint 17

[mnquintana]

Hmm, I wonder if this is because of all the packages consuming the status-bar service...

/cc @jlord

[Njke]

For me, status-bar is the only one in red zone. 😏

[lee-dohm]

The easy way to find out if it is because of other packages consuming the status-bar service would be if everyone can launch Atom cold by:

1. Completely exiting all instances of Atom
2. Launch Atom using atom --safe
3. Report your Timecop results before and after

[stramel]

@lee-dohm This is "safe" mode opening with a folder of only 4 files.

However, when I load my normal project folder on open in safe mode and it opens a bunch of files that were opened when it closed. Every system plugin was in the red on the very first load.

[kubetz]

@lee-dohm @mnquintana

I tried to profile status-bar startup in a very primitive way. I set a breakpoint on the 1st line of status-bar/lib/main.coffee and then profiled the activation of the status-bar package using Developer Tools.

What I found out is that DeprecationCopStatusBarView.updateDeprecatedSelectorCount() was called 82 times. After that I disabled deprecation-cop package to check the performance differences.

Here is the output of profiling for you too load in Developer Tools.

Enabled deprecation-cop:

Disabled deprecation-cop:

I hope it helps at least a bit! 🍻

[jerone]

Complete new Windows install today, so complete new install of Atom, running for the second time, resulting in:

Atom 1.0.0
Windows 8.1 64-bits

[flashus]

I have problems with status-bar git part. When I open git repository it takes long time to open files there. Atom started from cmd atom --safe

Profiling point to GitRepository.prototype.getDiffStats:

My system:
Atom 1.3.2,
Windows 7 x64,
git version 1.9.5.msysgit.1

I've tried to speed up git http://stackoverflow.com/questions/4485059/git-bash-is-extremely-slow-in-windows-7-x64
$ git config --global core.preloadindex true
$ git config --global core.fscache true
$ git config --global gc.auto 256
But it doesnt help.

[lee-dohm]

@flashus I suspect that you have a new underlying issue that we'll need to investigate separately. Would you open a new Issue please?

It also appears that this Issue was fixed by atom/deprecation-cop#56, so I'm going to close this.

[icearith]

I still got this issue

[lee-dohm]

@icearith Slow activation time is a symptom of an underlying problem. Once we have a better idea of what is causing the problem you're experiencing, then we can open an Issue on the correct repository. For general support questions like this, please post on Discuss, the official Atom message board and I, or someone else from the community, will help you narrow down the root cause.