-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Massive memory usage (1.4GB) #178
Comments
+1 on "doesn't quit" and "manual sync". |
Hey @scratchfive — have you updated to 0.3.19? There was a pretty bad memory leak in earlier versions which was fixed in ad52740. If you run into that memory issue on 0.3.19, it'd be great if you could run a Heap Snapshot in the Chrome Developer Tools and post the output here. It provides some pretty amazing detail and we can see specifically what we need to fix. To submit a heap snapshot, do the following in the app's main window, and also in the work window (which you can show via Press Cmd-Opt-I to open the Developer Tools, then choose "Profiles" from the top menu. Click "Take Heap Snapshot" and then "Take Snapshot". In the sidebar it'll say "Snapshot 1". Choose "Save" and send it our way! |
Currently running build 0.3.19-de7d1bb. I've attached a link to an archive containing the heap snapshots requested as they are rather large. https://www.dropbox.com/s/bgryu8uc2aexqbl/heapfiles.7z?dl=0 |
Hey folks, Thanks for the heap trace @scratchfive — I should be able to diagnose the problem based on that. Unfortunately, 1.4+ GB is an issue, but 300-400MB of RAM is the expected memory usage. I agree that 400MB or RAM is /also/ a crazy huge amount, but N1 is built on Chromium and is equivalent to running Chrome with 5 tabs fairly large open. Chrome unfortunately uses about 50-100MB of RAM per tab: Chromium has been working to reduce this, and Chromium 45 uses less memory. We haven't moved to it yet, but we plan on doing so as soon as it's stable. |
Ah, the Chromium core is definitely the issue. 400mb is the usage at startup, but it was reaching a monumental amount after being open for a while (it was open for about 2 days, with a few computer sleeps in between). I'll post a screenshot when it occurs again. Funny thing is that I just noticed that a NYT infographic/animation article on Hurricane Patricia was open in a background Chrome Window (minimized) and when I closed it, my memory usage went from about 5.2Gb to 2.8Gb! Insane memory leak on Chrome's end; good I just reported it to them. |
Yeah—we have plans to cut memory usage within the app by being smarter about how we hold your contacts in memory, fixing leaks found in heap files, etc... Fixing leaks is totally doable and the app should never use 1.4GB of RAM. At the end of the day though, I think we'll get memory usage down to about ~350MB all the time, but it's unlikely it'll go any lower because it's Chromium under the hood. |
Totally understandable! Hopefully Chromium will continue to improve its memory usage also. |
I also came along this issue. Just to let you know: On my Macbook 12" the Electron Helpers are taking up a total of 643MB and additionally the Nylas N1 process about 76MB. Sums up to a total of 719MB. Still a lot of memory usage, especially when you consider the lower hardware specs of my model. By the way, I have four email accounts connected - how big is the effect on memory usage when adding additional accounts, do you know that? I might delete some otherwise. |
As another data point, I have 2 accounts setup. Electron helper uses just over 1GB. Nylas is using 61MB. |
Is still an issue? |
@mbilker I am seeing about 450MB with Electron Helper and Nylas with 2 accounts setup. Definitely seems to be an improvement for me and close to the goal of "~350MB all of the time". |
@patrickheeney well that is better. Under my Linux setup I see around that, but I am not always sure because of shared memory, GPU memory maps, |
It's also down for me. Around 500MB. Thanks. |
On Ubuntu 15.10 there are 7 threads open with a combined memory usage of almost 1 GB. |
That is normal since N1 uses Chromium's process model.
|
While it may be normal, is it really desirable that an email client requires a gb of memory? |
It is being worked on, but the focus currently on features and bug fixing. |
That's good @bertrand47. I notice the same under |
It's also like that on windows now (it should use even less RAM than your screenshot). |
I know this was closed but the latest build is still using, 1GB+ of RAM on my MBPr anything else I need to provide? |
N1 if left open will eventually consume about 1.4 gigs of my RAM which is quite excessive. This is collective and includes the electronJS processes that are spawned.
The text was updated successfully, but these errors were encountered: