microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception Freeze in EDT for 28 seconds Sampled time: 14400ms, sampling rate: 100ms, GC time: 710ms (2%), Class loading: 0%, CPU load: 3% com.intellij.diagnostic.Freeze
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 262
- Forks
- 185
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
IntelliJ build version: 2025.1.1.1 IC-251.25410.129
OS: Windows 11
JDK: JetBrains s.r.o. 21.0.6
Plugin version: 3.95.0-2025.1
Additional Info: None
Parent component:
com.intellij.openapi.wm.impl.IdeRootPane[,7,7,1536x816,layout=com.intellij.openapi.wm.impl.IdeRootPane$CustomHeaderRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]
Error message:
IdeaLoggingEvent[message=Freeze in EDT for 28 seconds
Sampled time: 14400ms, sampling rate: 100ms, GC time: 710ms (2%), Class loading: 0%, CPU load: 3%, throwable=com.intellij.diagnostic.Freeze
at com.microsoft.azure.toolkit.lib.appservice.webapp.WebAppServiceSubscription.getRuntimesUsingHttpPipeline(WebAppServiceSubscription.java:114)
at com.microsoft.azure.toolkit.lib.appservice.webapp.WebAppServiceSubscription.loadRuntimesUsingHttpPipeline(WebAppServiceSubscription.java:96)
at com.microsoft.azure.toolkit.lib.appservice.webapp.WebAppServiceSubscription.loadRuntimes(WebAppServiceSubscription.java:61)
at com.microsoft.azure.toolkit.lib.appservice.model.WebAppRuntime.tryLoadingAllRuntimes(WebAppRuntime.java:157)
at com.microsoft.azure.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the stack trace in WebAppServiceSubscription.java, especially getRuntimesUsingHttpPipeline and loadRuntimesUsingHttpPipeline, then trace the call from WebAppRuntime.java. Investigate the reported IntelliJ freeze in the Azure App Service runtime-loading path; done means the reported EDT freeze no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, java
- Domain
- cloud, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100