John Gardner

No error messages then? Does everything work fine if you boot in regular (non-dev) mode?

Okay, this is because Atom's failing to start, indicating a *serious* error that's far beyond the scope of this package. You need to report this upstream. This can affect `file-icons`...

Either way, it's still bad. There's nothing in the `file-icons` package that could possibly trigger a crash; it's clear that whatever you're experiencing is unrelated to this package. Note that...

>…`devicons.ttf?xqxft6 Why does this URL end with a query string? > but cannot follow the path as I cannot "open" app.asar. Just for the record, you can unpack it using...

@kaiyoma Okay, that's bad. Is there anything unusual about the filesystem in which the affected files reside? E.g., is it a remote drive (like a network file-share)? Are you using...

@kaiyoma After clicking the "folder" which fails to open, do you see any error messages being displayed in the dev-console?

@kaiyoma Try disabling the package's modeline, hashbang, and `.gitattributes` strategies. This will stop `file-icons` from making any filesystem calls, which are most likely the catalyst. If this doesn't fix your...

**Settings** → **Packages** → Search for `file-icons` → Scroll down to **Match strategies**

@nszaaa3 Are you running any background tasks, like formatting with Prettier or something? If so, this might be caused by the issue @utkarshgupta137 brought up in [#693](https://github.com/file-icons/atom/pull/693#issuecomment-732107010). I'll prepare a...

Sorry for not looking into these issues (as well as unburdening package load time by making it asynchronous). 😞 I wanted to tackle them with a temporary solution at least,...