Created attachment 93049 [details]
Thread dump attached. The IDE completely froze up and CPU usage maxed out while editing a source file in a Maven web application
It looks like a deadlock between "AWT-EventQueue-1" and "Parsing & Indexing Loop (200912041610)". The AWT thread performs BaseKit$DefaultKeyTypedAction which write-locks the document and then through TextRegionManager and JavaCodeTemplateProcessor tries to run a userActionTask. At the same time there is some other userActionTask running, which tries to read-lock the document.
AFAIR the policy is to first lock the parser and then a document. So Strictly speaking the code running in AWT is at fault here. However, I have no idea how to fix the DefaultKeyTypedAction....
The only place that came to my mind where to fix this is CodeTemplateInsertHandler.notifyParameterUpdate
by posting the call to
into its own runnable in AWT.
After consulting with Mila I did not apply this change and I am passing to Dusan to evaluate whether it is really necessary to call runWhenScanFinished from getProposedValue(JavaCodeTemplateProcessor).
Dusane, can you please have a look at this one?
*** This bug has been marked as a duplicate of bug 186324 ***