Basically I'm wondering if there is any way to fix this other than to turn it off?

We have a pretty complicated pom heirarchy, going down 4-5 levels.

What I find is that when I run something from in the IDE, it blocks for 30 seconds - 2 minutes, spinning the CPU.

Doing a pkill -3 java shows this kind of stack, often:

"AWT-EventQueue-1" prio=10 tid=0x00007f4780004400 nid=0x4e99 runnable 0x00000000414b7000..0x00000000414b8b90

   java.lang.Thread.State: RUNNABLE

     at gnu.trove.TObjectHash.index(TObjectHash.java:205)

     at gnu.trove.THashMap.get(THashMap.java:356)

     at com.intellij.openapi.util.objectTree.ObjectTree.getNode(ObjectTree.java:42)

     - locked (a java.lang.Object)

     at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)

     at java.awt.EventQueue.dispatchEvent(EventQueue.java:597)

     at com.intellij.ide.IdeEventQueue.c(IdeEventQueue.java:35)

     at com.intellij.ide.IdeEventQueue.b(IdeEventQueue.java:99)

     at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:217)

     at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:273)

     at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:183)

     at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:173)

     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:168)

     at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:160)

     at java.awt.EventDispatchThread.run(EventDispatchThread.java:121)

The longer I run the IDE (or rather, the more times I run an application), the longer the delay.

Disabling the maven plugin seems to fix the problem.

Anybody else seeing this?  Anybody from jetbrains care to comment?

Thanks,

Eric