Community
Participate
Working Groups
Created attachment 139861 [details] Error log file portion relevant to error I am running PDT 2.1 RC5 with a Moodle-based project, and it seems the build feature is collapsing and running out of memory when trying to build the PHP environment in the background, possibly due to the size of the project itself. I've attached a clip from my error log file resulting from the crash, as well as a PNG screenshot of the error that pops-up.
Created attachment 139862 [details] Screenshot of error window
Hi, can you please describe the project management settings you have, such as the values of your include path and buildpath, you .project setting. thanks for your report,
Created attachment 139873 [details] .settings & .project, no .buildpath (deleted accidentally)
Hi, From the log you attached it seems that the errors thrown to the log concern some issues with: 1. Eclipse Platform - Resource is not sunced 2. JSDT - NullPointerException org.eclipse.wst.jsdt.internal.compiler.flow.UnconditionalFlowInfo.markAsDefinitelyNonNull(UnconditionalFlowInfo.java:1192) Since the "resource is not sync" issue can be solved pretty easy by refreshing your workspace I will leave this bug to the JSDT team who should check the thrown exceptions NullPointerException at org.eclipse.wst.jsdt.internal.compiler.flow.UnconditionalFlowInfo.markAsDefinitelyNonNull(UnconditionalFlowInfo.java:1192) at org.eclipse.wst.jsdt.internal.compiler.ast.FieldReference.analyseAssignment(FieldReference.java:81) at org.eclipse.wst.jsdt.internal.compiler.ast.Assignment.analyseCode(Assignment.java:59) at org.eclipse.wst.jsdt.internal.compiler.ast.MethodDeclaration.analyseCode(MethodDeclaration.java:94) at org.eclipse.wst.jsdt.internal.compiler.ast.AbstractMethodDeclaration.analyseCode(AbstractMethodDeclaration.java:112) at org.eclipse.wst.jsdt.internal.compiler.ast.FunctionExpression.analyseCode(FunctionExpression.java:73) at org.eclipse.wst.jsdt.internal.compiler.ast.ObjectLiteralField.analyseCode(ObjectLiteralField.java:78)
Hi Basil, I was wondering if you could provide any more information on what caused these errors. I took a look at your stack trace and from that I determined you probably had JavaScript statements in the form of... function MyClass() { this.myField = 1; } var oLit = { a: function() { var myClass = new MyClass(); myClass.myField = 3; } }; From that I wasn't able to reproduce the NPE in UnconditionalFlowInfo. Do you still have the source that caused this problem? I'm also wondering if your resources being out of sync caused JSDT not to be able to resolve everything correctly. That could have caused an error as well. Thanks, Chris
I have been unable to reproduce this problem. If you experience this error again please re-open and provide the information I requested in comment #5 on July 15. Thanks, Chris
