Bugzilla – Full Text Bug Listing
| Summary: | Eclipse freezes during: Building workspace -> Starting mojoExecution aspectj:compile | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Eduardo Simioni <simioni.eduardo> | ||||
| Component: | IAM | Assignee: | Project Inbox <iam.Core-inbox> | ||||
| Status: | NEW --- | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 193564 [details]
Thread Dump
The thread I suspect that is causing the problem: "Thread-1" daemon prio=2 tid=0x66d03000 nid=0x520 waiting on condition [0x6957f000] java.lang.Thread.State: WAITING (parking) at sun.misc.Unsafe.park(Native Method) - parking to wait for <0x1f7f9d38> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject) at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1987) at java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:317) at org.eclipse.equinox.weaving.internal.caching.CacheWriter$1.run(CacheWriter.java:47) at java.lang.Thread.run(Thread.java:662) Locked ownable synchronizers: - None |
Build Identifier: 20110301-1815 Eclipse freezes very often when I clean the projects (Menu: Project -> Clean... -> Clean all) It starts cleaning and compiling all projects an then hangs. In the progress view it stops at: "Building workspace -> Starting mojoExecution aspectj:compile". The freeze always happens in this step. During the freeze Eclipse is using 100% of a CPU core and the UI becomes unresponsive. I took some thread dumps at this stage, they don't look different from each other (kind of expected), so I attached just one. I use Aspects in some projects and I have AJDT installed. I'm not sure if the bug is in IAM, sorry if it is not, but looks like it is, or at least it is involved somehow. Two projects in my workspace are using Aspect weaving with the following build configuration in the POMs: <build> <plugins> <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>aspectj-maven-plugin</artifactId> <version>1.3</version> <dependencies> <dependency> <groupId>org.aspectj</groupId> <artifactId>aspectjtools</artifactId> <version>1.6.8</version> </dependency> </dependencies> <configuration> <complianceLevel>1.6</complianceLevel> <target>1.6</target> <source>1.6</source> <verbose>true</verbose> <showWeaveInfo>true</showWeaveInfo> </configuration> <executions> <execution> <goals> <goal>compile</goal> <goal>test-compile</goal> </goals> </execution> </executions> </plugin> </plugins> </build> The environment is: Windows 7 Professional 32-bit Java HotSpot(TM) Server VM (19.0-b09 mixed mode) Please let me know if you need further information. I don't have a receipt to reproduce it, but it happens 5-10 times a day for me. The thread dump is attached. Reproducible: Sometimes