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
Pub running out of memory #19174
Comments
Do you get this if you run pub from the command line? Can you run with --verbose and include the results? Added NeedsInfo label. |
There's no further info. This was anonymous user feedback. Sorry, I forgot to switch the template. Added Triaged label. |
In that case, there's not really anything else we can do here. Added CannotReproduce label. |
This comment was originally written by @zoechi This seems to be from me. |
This comment was originally written by @zoechi I still have this after the update to |
Removed Priority-Unassigned label. |
This comment was originally written by @zoechi It seems that my growing entry_points list is causing the issue. It seems I commented out all but one entry page and the start up is way faster than recently and the page is served reliably. Maybe the already discussed lazy transformers help here too. transformers:
|
Ah, thanks for the details. This sounds like the memory usage is in the polymer transformers then. Making them lazy would likely help here, but that hasn't happened yet. I'm bouncing this to Siggy, but I would like to still be involved here and see if there's anything we can do in pub/barback to help. Set owner to @sigmundch. |
I'm marking this as blocked on getting lazy transformers in place. After that, we still need to investigate what to do after we run the transformers. For example, we should ensure that the transformers's state & analyzer data can be collected after we run a transformer on an entrypoint. Removed this from the 1.5 milestone. |
Removed this from the 1.6 milestone. |
Removed Polymer-P-1 label. |
Added PolymerMilestone-Next label. |
Removed Polymer-Milestone-Next label. |
Added this to the 1.6 milestone. |
Removed this from the 1.6 milestone. |
Added this to the 1.6 milestone. |
This issue has been moved to dart-archive/polymer-dart#401. |
[ed note: It looks like pub is running in the screenshot. The error message is from the vm (heap.cc). I'm not sure if the large editor memory allocation could be causing everything else to be starved, tho -- we don't know the RAM size]
'I get this `Exhausted heap space, ...' permanently.
I can hardly launch any example. Sometimes it starts before this error occurs, but most of the time it doesn't.
////////////////////////////////////////////////////////////////////////////////////
Editor: 1.5.0.edge_036922 (2014-06-03)
OS: Linux - amd64 (3.13-1-amd64)
JVM: 1.7.0_55
projects: 25
open dart files: 4
auto-run pub: true
localhost resolves to: 127.0.0.1
mem max/total/free: 3556 / 1511 / 767 MB
thread count: 43
index: 663655 relationships in 97915 keys in 655 sources
SDK installed: true
Dartium installed: true
The text was updated successfully, but these errors were encountered: