MAC: atom --profile-startup doesn't work on 1.12.0

[ungb]

Bug: running atom --profile-startup in terminal doesn't work

Steps to Reproduce

1. Make sure you have latest installed from atom.io (currently it is 1.12.0).
2. run: atom --profile-startup

Expected behavior: Open Atom with dev tools open showing how long it took to load to startup
Actual behavior: For me, it just crashes. Atom doesn't open.

Versions
Atom: 1.12.0
apm: 1.12.9
macbook pro 2015: 10.12.1

[Alhadis]

I came here to report similar behaviour with atom --dev, probably related.

Output of apm --version:

apm: 1.12.9
npm:  3.10.5
node: 4.4.5
python: 2.7.12
git: 2.10.2

Operating system: macOS Sierra v10.12.1
Executed path: /Applications/Atom.app/Contents/Resources/app/atom.sh -d

This is still happening even after I:

1. Cleared all caches and storage directories in ~/.atom
2. Uninstalled and reinstalled Atom
3. Repeated step two after rebooting my computer
4. Removed all packages from ~/.atom/dev/packages

Every attempt to start Atom in dev-mode was greeted with the same result:

[ungb]

@Alhadis I'm not sure if it's related, but one thing you can try is if you have atom repo checked out in ~/github/atom. Try moving that directory and launching atom again with --dev.

1. Close all Atom instances
2. mv ~/github/atom ~/github/atom_backup
3. atom --dev

If you don't have Atom repo in ~/github/atom, it could be located where the environment variable ATOM_DEV_RESOURCE_PATH is set.

[Alhadis]

Nope, and there're no ATOM_* variables except $ATOM_THEME, which is just a shortcut pointing to my heavily-customised Atom setup (that takes the form of a syntax theme... don't ask).

So as far as I can tell, there's no obvious reason this should be happening... :\

Also, this affects windows that're opened from within Atom using the Open in dev-mode command...

[ungb]

do you have the repo checked out in ~/github/atom?

[Alhadis]

No. I'm running a stable version; I just upgraded to Atom v1.12.0 earlier before...

[Alhadis]

This mightn't be related after all; I've narrowed the culprit down to a language package I had installed, which is causing the editor to crash when it's opened in dev-mode (for reasons I've yet to determine).

So far, my theory is it might have something to do with needing to rebuild native modules or something... the language-csound package has first-mate as a hard dependency, which in turn requires oniguruma (that needs compiling). Otherwise, I'm drawing blanks here.

UPDATE: Running apm rebuild && apm install in the installed package's directory fixed the problem. No idea how this could be related to dev-mode, though.

UPDATE II: Spoke too soon, I think it might've silenced the problem instead of fix it:

Running apm rebuild in ~/.atom/packages/language-csound achieves nothing, so... not sure what's going on here. I'll let the package author know the dependencies are causing issues.

---

@ungb What packages do you have installed/enabled? Can you confirm if this issue still occurs after running apm install in every installed package's directory?

[lock]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!