So, good work on continuing to update and add features, however, I have a small (well, ok, large) issue for you, I’ll also open it in the repo.
Atom CPU usage before opening term2
Atom CPU usage with term2 open.
So I thought it might be an issue in that I was running a watch task in there (standard grunt watch task, nothing fancy), so I tried just opening term2:
CPU usage immediately after opening term2 into a new right pane.
Also tried just opening up a different pane without term2 in there to make sure Atom wasnt playing silly buggers, no problems, its deffo term2.
edit Oh, I should add this is with OSX 10.8.5 on a non-retina MBP.