is anyone else finding the current plugin release to be quite buggy? lots of long hangs, stalls, sometimes all intellisense-style features just randomly die for 10-30 seconds (typing works but nothing highlights and calling up completion yields a completely empty list)

if it's just me i guess i'll make some time to debug it

I had some issues yesterday too, a couple of random crashes.

if it's a known issue i'll leave it

which version are you using ?

of the plugin

Version: 1.1.3-release-IJ2017.1-2

can you file a YT issue and attach the thread dumps from the logs directory?

ah! i'd opened the logs dir in the finder but didn't scroll down. you mean the threadDumps-freeze-42sec type folders? great idea, i'll have a rummage in them and submit a bug report

yes. you can just zip all of them and we'll sort them out

thanks

That's the same as pressing "report", right?

no, "report" is for exceptions, thread dumps are for diagnosing poor UI responsiveness

ah .... i am looking at some dumps myself

i spy this:

at no.tornado.tornadofx.idea.FXTools$Companion.isTornadoFXType(FXTools.kt:36) at no.tornado.tornadofx.idea.framework.TornadoFXFrameworkDetector.detect(TornadoFXFrameworkDetector.kt:36) at com.intellij.framework.detection.impl.FrameworkDetectionManager.a(FrameworkDetectionManager.java:228)

on the AWT thread

so apparently my TornadoFX plugin is doing some heavy type resolution on the UI thread. I'll try disabling the TornadoFX plugin and see if that helps.

this leads to an idea - when intellij does a stack dump on freeze, it could identify which plugins were on the stack of the AWT thread at the time and pop up a hint

once TornadoFX plugin tries to detect whether the framework is in use on the AWT thread, it then goes like 100 frames deep into the type resolution code. at the time the snapshot was taken, it was sitting in JavaTypeResolver.computeTypeConstructor.

i'll report this to edvin too. perhaps he's doing it wrong (or just more inefficiently than intellij expects)

I wouldn't blame tornadofx here. the key issue in play here is https://youtrack.jetbrains.com/issue/KT-18921, which is what I'm working on right now, and https://youtrack.jetbrains.com/issue/KT-18900 is also related

hmm right. in other thread dumps I see it was trying to detect JUnit instead, and ended up spending a lot of time resolving superclasses and things too. so I guess it's KT-18900

ok, looking forward to 1.1.4!

I'll see if I can improve the detection feature in the TornadoFX plugin as well 🙂

well, it sounds like i was just "firing from the hip" as they say 🙂

perhaps the operation you're invoking is supposed to be very fast. the fact that intellij runs it on the ui thread and the junit plugin does the same thing, apparently, suggests that maybe it's the case.

i don't know much about intellij internals.

Yeah, as I understand it, I'm just traversing an already established object graph so I don't know if there is much to improve.