Community
Participate
Working Groups
Build Identifier: Juno M7 J2EE - 20120510-1218 There are still major memory/performance issues with mid-size/large projects. I am unable (or at least I have to wait for a very long time) to work with some of my dynamic web projects in eclipse juno. Unfortunately, I am not able to submit the project here, but I wrote a simple generator which creates a similar-sized project (2000 class files, 500 jsps, 20000 warnings) which shows similar issues. Beside the memory/performance issues, this project shows several other issues (open some jsps and try to make some changes), but this is not the crucial part of this report. I am not sure if this is only related to webtools - but for my initial report, I file it within this component. (Once the opening of those projects corrupted some javascript indexes and I was not able to use eclipse anymore (some kind of EOFException in the JSDT parser). Reproducible: Always Steps to Reproduce: 1. Download Juno M7 J2EE package 2. Open Juno M7 J2EE 3. Disable build automatically 4. Import the project (import->existing projects into workspace -> from archive file) 5. Create a new runtime, using tomcat 6.x 6. Check build path settings of project and bind that runtime to the project 7. Enable build automatically 8. From now, look at memory/cpu/time usage 9. If the compile succeeds, trigger a clean build 10. Repeat Step 9 several times 11. Optional step: Try to work with the IDE while the build is running 12. Optional step: Open some jsps.
Created attachment 216193 [details] an example (auto generated) project
Patric, any of the stack traces you did encounter with your real data would still be of interest.
Beside the exceptions the main issue which can be seen in both the real life project and the submitted test project is performance/memory consumption/OutOfMemoryErrors. This is the reason why I put in significant efforts to provide you a test project. I really encourage you to give it a try and to see what's going on/wrong. I played some more hours with webtools with my real projects - you can find all exceptions which occurred in the attachment below.
Created attachment 216271 [details] exceptions which occurred in webtools while working with real projects
*** This bug has been marked as a duplicate of bug 359005 ***
Nitin, I do not see why this bug should be a duplicate of bug 359005. This bug is about crashes/performance/memory consumption with greater projects while bug 359005 seems to be about a specific NPE.
Patric, it's the only one I can (still) reliably reproduce, even after multiple cleans and builds. The JsTranslator exceptions from your log were fixed in 3.4.1, and the others look like the workbench itself was either shutting down or in an odd state where code was being called while the plug-in was not started or already stopped.
Good news. Does this mean that the performance/memory issues mentioned in the bug description are fixed as well?
Only that I have not been able to reproduce them with your project, 10+ JSP files opened and editors activated, and numerous rebuilding of the workspace.
