Summary: | Too frequent build requests | ||
---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Philipe Mulet <philippe_mulet> |
Component: | Core | Assignee: | JDT-Core-Inbox <jdt-core-inbox> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | P3 | CC: | daniel_megert, jerome_lanneluc, john.arthorne |
Version: | 3.2 | ||
Target Milestone: | 3.3 RC4 | ||
Hardware: | PC | ||
OS: | Windows XP | ||
Whiteboard: |
Description
Philipe Mulet
2006-06-09 09:11:28 EDT
This looks like someone failng to properly batch operations. Each message like this: [org.eclipse.jdt.internal.ui.text.JavaReconciler] Build requested, needsBuild: false state: 1 delay: 516 Means someone called "Workspace.run(IWorkspaceRunnable). The "needsBuild: false:" means that they didn't actually make any changes. This doesn't mean that a build has been started. Moving to JDT text since most of these messages come from the Java reconciler thread. John, the reconciler thread doesn't call Workspace.run(...). No clue what I should do with this bug. Philippe, is it possible that JCore does this when we call reconcile(...)? Jerome would know. I think we do batch all the pieces. My impression is that it occurred only once, i.e. I am wondering about a timing issue or something related. Moving to JDT Core for investigation. Please move back if you have more details why it is JDT Text related. Steps to reproduce would also be good. If containers are being initialized during reconcile, projects can be touched (IProject#touch()) to force a build. Could that be the case ? The "needsBuild: false" indicates that there are no changes in the resource tree, so IProject.touch() isn't being called in most of these cases. It just looks like dozens of IWorkspace.run(..) calls with no actual changes... Note that this isn't necessarily a problem. I think the "Build requested" debug statement is misleading, because it doesn't actually indicate that a build will occur. It just means a top-level workspace operation has completed. Closing since the trace doesn't indicate real build requests. |