Even though I run across this issue so often, I cannot even think of leaving Atom. Of course it has become 2nd nature that when I accidentally click on something like jquery, or some other 20-100kb file where I lose functionality, I close Atom, and start again. It’s 3-4 seconds of inconvenience, but thanks to auto-save, no harm, no foul.
To attempt to offer some insight, I’m curious why the file has to be completely loaded in the immediate view, especially when the size is problematic. I want to say that systems like CodeMirror only run syntax highlighting on the viewable area, and stream the rest when in view, instead of trying to run everything through the tokenizer all at once (Please correct me if I’m wrong about this). I’m sorry, I really do not know enough about Atom’s viewer, but can anything like this happen, at least with certain sized files?
I have also noticed that it depends on memory. Sometimes opening a minified file, or jquery file doesn’t cause any issues, but if accidentally hit more than one during this time, it’s game over. The point being that at some point Atom can handle these, but I’m guessing this is dependent on how long I have had Atom open, and how many files the view has seen causing a fluctuation in the current memory usage. I don’t know, but I thought I would at least share.