Skip to content
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

Creating optmized js from editor causes out of memory #537

Closed
DartBot opened this issue Nov 19, 2011 · 5 comments
Closed

Creating optmized js from editor causes out of memory #537

DartBot opened this issue Nov 19, 2011 · 5 comments
Assignees

Comments

@DartBot
Copy link

DartBot commented Nov 19, 2011

This issue was originally filed by [email protected]


Compiling this
http://bit.ly/uZnEH6

 to optimized js from the editor (build 1584) causes:

Error compiling library: file:/dartexamples/dynamiclist/basicajax.dart
java.lang.OutOfMemoryError: Java heap space

@devoncarew
Copy link
Member

We have some changes coming down the pipe that should reduce memory usage; in the meantime, you can increase the maximim heap of the editor by editing the DartEditor.ini file. The line you want to change is the -Xmx line.

You can find the DartEditor.ini file in the same directory as the executable. On the Mac, you have to right click the application and choose 'Show Package Contents'. The ini file is a few directories down in Contents/MacOS.


Added Area-Editor, Triaged labels.

@DartBot
Copy link
Author

DartBot commented Nov 20, 2011

This comment was originally written by [email protected]


With 1048m it is working

@devoncarew
Copy link
Member

Set owner to @devoncarew.
Added Accepted label.

@devoncarew
Copy link
Member

From feedback: I keep getting "java.lang.OutOfMemoryError: Java heap space" when I try to compile my simple dart project to "optimized javascript." I would copy+paste the stack trace, but its very large.

@devoncarew
Copy link
Member

The dartc team just landed some tree-shaking changes that will make the generated javascript much smaller. When this new output gets fed into the jscompiler (the --optimize step), we should no longer see the out of memory problems.

Our next integration builds (and the current continuous build) will pick up these changes. Please re-open this if you still see the problem!


Added Fixed label.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants