Bugzilla – Full Text Bug Listing
| Summary: | Java heap space error in UI on refactoring of Javascript variable. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] JSDT | Reporter: | Vadim Yusanenko <usanenko.vadim> | ||||
| Component: | General | Assignee: | Project Inbox <jsdt.javascript-inbox> | ||||
| Status: | RESOLVED DUPLICATE | QA Contact: | Victor Rubezhny <vrubezhny> | ||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | daniel.rolka, shr31223, thatnitind | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | Macintosh | ||||||
| OS: | Mac OS X | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Vadim Yusanenko
You can increase the JVM heap size by proper options in the 'eclipse.ini' confiruration file (-Xms and -Xmx). You can also play a bit with different gc types in order to additionally tune your JVM. For Oracle JVM you can try to use the G1 one (-XX:+UseG1GC) Daniel Did it already: -Xss2m -Xms1G -Xmx1G It is not OK, when with such configuration I am out of heap space, it is definitely a bug. Regarding: -XX:+UseG1GC - grateful, make come in handy later, thanks. I will try to provide minimal sample project with this. I understand it is hard to debug with comments only. But maybe there is already a known limitation here, that you are aware of. Created attachment 248089 [details]
Minimal sample to cause heap space exception in WTP on refactor of var
1. Eclipse 4.4.1 and install WTP (JsDT is of interest here)
2. Unzip
3. Import as project
4. Configure as javascript project (if required)
5. Open "static/js/functions.js"
6. Right click on "current_row_iterator" variable and select refactor
I like Open Source movement and think Eclipse is a tool made with a good intent in mind. But let's be honest - to make it better - it is important to criticize it as well. Even the most loyal to Eclipse people (they are suffering but understand what it costs to create open source IDE and that it requires time and efforts :) ) agree that Web development in Eclipse is very poor at this moment. The sample I've attached is only 1/4 of all JS code we have, and if it can not handle this - it is not a production grade web IDE - it is only suitable for university homework. Sorry for such harsh words. A few thoughts (though I am a back-end developer, so may be wrong - sorry) - I declared variable in local scope (var XYZ) - is it really necessary to use all available memory to check whether this change will affect anything? It seems the only thing that may be affected is my function scope. Sorry if this question is dumb. - Once again - this is only a small part of all JS code available, if it can not handle this with MaxPermSize=1G, then something is really really bad in my opinion. Thanks for working on WTP and thanks for all criticism you are hearing. I do believe WTP will become better over time. Lot's of work here, I understand. Vadim, Your issue duplicates Bug #433515 which was fixed in Mars stream. There was a Feature Patch created due to address the issue in WTP Luna SR2 (See Bug #461160). You need to upgrade your Eclipse and WTP to be at least Luna SR2 and then install JSDT Feature patch for WTP SR2 from the repository: http://download.eclipse.org/webtools/repository/luna/ Thanks for your patience! *** This bug has been marked as a duplicate of bug 433515 *** |