-
Notifications
You must be signed in to change notification settings - Fork 325
Infinite spinner while trying to load property editor #8144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Attaching a spinning ball case: |
I think the attachment is missing. I had to add .txt to the file extension to get github to accept it. |
I can reproduce this in Android Studio. I saw it consistently yesterday, however today I was able to load the property editor once, however it usually fails. When it fails, the property editor connects to DTD and connects to the Service stream, but it is not told about any services (like the Editor services), and therefore doesn't initialize. I enabled the analysis server instrumentation log and confirmed that Android Studio was calling When I review my running processes, I can see a single DTD instance, and I can see that DevTools was started with a DTD URI that matches the one the analysis server connected to.. However I also see another DevTools running, that does not have a Based on this, my current theory (with zero knowledge of how the plugins work) is that Android Studio is somehow spawning two DevTools servers. One is correctly being provided a DTD URI (for the DTD that Android Studio started), but the second is not, and is therefore spawning its own DTD, and that's the server being used by the Property Editor panel. Since this is intermittent, I wonder if there is a race here, and when it works, only one DevTools server was spawned (or, both were spawned after DTD was started and therefore were provided the same/correct DTD URI). |
I missed it in the list before, but I do also see the second instance of DTD in the process list, but it is spawned as I don't think I know enough about the plugins to debug this any further, but perhaps it will be useful to someone more familiar with them. |
@jwren @alexander-doroshko I had a quick search across the plugin code to see if I could spot anything. I found that DevTools is spawned here: The Fixing that (for example by setting |
I did as well, but it keeps getting rejected by GitHub. |
Successful load (remove .txt to load in Chrome DevTools):
successful_load.har.txt
@jwren @elliette
The text was updated successfully, but these errors were encountered: