this plugin crashed with vasp code within clion 2019.2.

[hongyi-zhao]

Hi,

I'm using clion 2019.2, I installed this plugin and open some source files of vasp 5.4.1.

Then I find the this plugin crashed with the following info:

---

ase.lambda$getValueWithLock$1(CachedValueBase.java:240) at com.intellij.openapi.util.RecursionManager$1.doPreventingRecursion(RecursionManager.java:113) at com.intellij.openapi.util.RecursionManager.doPreventingRecursion(RecursionManager.java:71) at com.intellij.util.CachedValueBase.getValueWithLock(CachedValueBase.java:241) at com.intellij.psi.impl.PsiCachedValueImpl.getValue(PsiCachedValueImpl.java:43) at com.intellij.util.CachedValuesManagerImpl.getCachedValueFromExHolder(CachedValuesManagerImpl.java:72) at com.intellij.util.CachedValuesManagerImpl.getCachedValue(CachedValuesManagerImpl.java:45) at com.intellij.psi.util.CachedValuesManager.getCachedValue(CachedValuesManager.java:147) at com.intellij.psi.util.CachedValuesManager.getCachedValue(CachedValuesManager.java:129) at org.jetbrains.fortran.lang.types.ExtensionsKt.getInference(Extensions.kt:11) at org.jetbrains.fortran.ide.inspections.FortranTypeCheckInspection.collectDiagnostics(FortranTypeCheckInspection.kt:16) at org.jetbrains.fortran.ide.inspections.FortranTypeCheckInspection.access$collectDiagnostics(FortranTypeCheckInspection.kt:10) at org.jetbrains.fortran.ide.inspections.FortranTypeCheckInspection$buildVisitor$1.visitMainProgram(FortranTypeCheckInspection.kt:12) at org.jetbrains.fortran.lang.psi.impl.FortranMainProgramImpl.accept(FortranMainProgramImpl.java:27) at org.jetbrains.fortran.lang.psi.impl.FortranMainProgramImpl.accept(FortranMainProgramImpl.java:31) at com.intellij.codeInspection.InspectionEngine.acceptElements(InspectionEngine.java:75) at com.intellij.codeInsight.daemon.impl.LocalInspectionsPass.lambda$null$8(LocalInspectionsPass.java:321) at com.intellij.util.AstLoadingFilter.lambda$toComputable$2(AstLoadingFilter.java:169) at com.intellij.util.AstLoadingFilter.disallowTreeLoading(AstLoadingFilter.java:127) at com.intellij.util.AstLoadingFilter.disallowTreeLoading(AstLoadingFilter.java:116) at com.intellij.util.AstLoadingFilter.disallowTreeLoading(AstLoadingFilter.java:111) at com.intellij.codeInsight.daemon.impl.LocalInspectionsPass.lambda$visitRestElementsAndCleanup$9(LocalInspectionsPass.java:320) at com.intellij.concurrency.ApplierCompleter.execAndForkSubTasks(ApplierCompleter.java:133) at com.intellij.openapi.application.impl.ApplicationImpl.tryRunReadAction(ApplicationImpl.java:1106) at com.intellij.concurrency.ApplierCompleter.lambda$wrapInReadActionAndIndicator$1(ApplierCompleter.java:105) at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:591) at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:537) at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:59) at com.intellij.concurrency.ApplierCompleter.wrapInReadActionAndIndicator(ApplierCompleter.java:116) at com.intellij.concurrency.ApplierCompleter.lambda$compute$0(ApplierCompleter.java:96) at com.intellij.openapi.application.impl.ReadMostlyRWLock.executeByImpatientReader(ReadMostlyRWLock.java:164) at com.intellij.openapi.application.impl.ApplicationImpl.executeByImpatientReader(ApplicationImpl.java:204) at com.intellij.concurrency.ApplierCompleter.compute(ApplierCompleter.java:96) at java.base/java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:746) at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1020) at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1656) at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1594) at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:177)

[satamas]

I'm currently on vacation and can't take a close look for now. I've re-runed tests against release version of CLion and they passed successfully. I've also removed all deprecated method usages, but I doubt that this will change something. As a workaround you can disable FortranTypeCheckInspection, its current implementation isn't really useful anyway. I'll be back from vacation in a couple of weeks and will try fix it.

[hongyi-zhao]

Thanks a lot for your reply.

I just stay tuned for your updated version.

Regards

Semyon [email protected] 于2019年8月10日周六 上午12:39写道：

I'm currently on vacation and can't take a close look for now. I've re-runed tests against release version of CLion and they passed successfully. I've also removed all deprecated method usages, but I doubt that this will change something. As a workaround you can disable FortranTypeCheckInspection, its current implementation isn't really useful anyway. I'll be back from vacation in a couple of weeks and will try fix it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/satamas/fortran-plugin/issues/44?email_source=notifications&email_token=ACVDTDWGLBVC43XBU67OTU3QDWMVRA5CNFSM4IJTGSU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD37FRFQ#issuecomment-519985302, or mute the thread https://github.com/notifications/unsubscribe-auth/ACVDTDTKWLSA2MKPTD4TELDQDWMVRANCNFSM4IJTGSUQ .

-- Hongsheng Zhao [email protected] Institute of Semiconductors, Chinese Academy of Sciences GnuPG DSA: 0xD108493