Performance issues with Studio 7

Since installing the Studio 7 plug-in on IntelliJ Ultimate I’ve seen horrid decreases in performance, so slow I have to pause typing for the IDE to catch up. The logs show this

2019-02-18 20:39:30,096 [14882819]   WARN - eInsight.daemon.LineMarkerInfo - Performance warning: LineMarker is supposed to be registered for leaf elements only, but got: PsiErrorElement:'{' or ';' expected (class com.intellij.psi.impl.source.tree.PsiErrorElementImpl) instead. First child: PsiJavaToken:COMMA (class com.intellij.psi.impl.source.tree.java.PsiJavaTokenImpl)
Please see LineMarkerProvider#getLineMarkerInfo(PsiElement) javadoc for detailed explanations. 

Not sure if this is a clue. It doesn’t provide much information other than it’s presumably a plug-in. Interestingly it does warn of performance degradation and I certainly have that. I downloaded a fresh copy of Studio 7, using IntelliJ community edition, and saw the same error message. When this happens the only workaround is to exit the IDE, re-enter and cross your fingers you can get at least 15 minutes of solid work before having to repeat this cycle. Garbage collection gets very business around this time. Heap cycles in quick succession from around 500M to 1.3GB and then back down.

One last observation, this condition seems to be triggered or at least occurs around the same time as other numerous Studio 7 plug-in exceptions.

image

Here is some additional info. From the screenshot, you’ll notice the com.haulmont.studio.runconfiguration.process is consuming a large percentage of the CPU. This periodically appears to get “stuck” and never dips below 80% until I exit IntelliJ and re-enter. When I hear the fans on my Mac whirling up I know its time to restart.

Hi David,
We have a similar situation with one project on Mac and we are investigating the issue.

Hi David!

Could you take thread dump of Idea, when performance decreased, and attach it here? For taking the thread dump you can use Java VisualVM.

Also, please let us know if the problem persists after updating to Studio plugin v.7.4.