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
Improve the ability to share analysis between contexts #14489
Comments
Added Area-Editor, Triaged labels. |
cc @bwilkerson. |
This is basically a OOM situation with lots of swapping cased by the large number of Polymer projects (25 non-Polymer projects would not have the same problem). Polymer is quite large with a lot of dependencies. At the moment, each project gets its own copy of Polymer and its dependencies which gets fully analyzed independently of the other projects (since each could theoretically depend on a different version of the Polymer package). This will be optimized in the future so that each unique combination of Polymer and its dependencies will be analyzed once and result in a significant reduction in memory usage. This should eliminate the OOM errors that are seen in this case and the resulting swapping and performance degradation. There are couple of short terms workarounds that should help until we can put the above optimization in place.
cc @danrubel. |
Changed the title to: "Improve the ability to share analysis between contexts". |
Removed Type-Defect, Priority-Medium labels. |
Removed Type-Enhancement label. |
Removed this from the Later milestone. |
Added this to the 1.6 milestone. |
Removed Oldschool-Milestone-Later label. |
This is a reminder for a longer term goal. Removed this from the 1.6 milestone. |
This is now obsolete. |
This issue was originally filed by andrejnav...@yahoo.com
What steps will reproduce the problem?
Here are my observations with the latest versions of Dart Editor:
Editor anymore - see print screen [1]. To solve this problem I have followed
an internet advice, and I have deleted "-vmargs" option from "DartEditor.ini"
file.
small Polymer projects with maximum 100 lines of code per project. I've
noticed that during workspace initialization my laptop uses about 13% of
CPU power, and during that time the Dart editor is unresponsive. Analyzing
all projects takes very long time, about three minutes. With 'unresponsive'
I mean that I have to wait more than 5 seconds for a response of the
editor for a mouse click.
even without saving a file, and my Dart editor becomes unresponsive, sometimes
for about 10 seconds and sometimes even for about 45 seconds.
"Waiting for background analysis...". I receive the same message if I try
to rename a file 5 or 10 minutes later.
after I had already closed the Dart Editor.
Dart Editor a log file [2] is also included from my last two sessions. In the
log file a lot of Java "java.lang.OutOfMemoryError" exceptions could be seen.
[1] - could-not-create-the-java-virtual-machine.png
[2] - dart-editor.log.txt
What is the expected output? What do you see instead?
What version of the product are you using? On what operating system?
Windows 7
Dart Editor version 0.8.5_r28990
Dart SDK version 0.8.5.1_r28990
Please provide any additional information below.
Attachments:
dart-editor.log.txt (79.31 KB)
could-not-create-the-java-virtual-machine.png (45.98 KB)
The text was updated successfully, but these errors were encountered: