microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception Freeze in EDT for 27 seconds Sampled time: 17900ms, sampling rate: 100ms, GC time: 173ms (0%), Class loading: 0% 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.2.3 IU-252.26830.84
OS: Mac OS X
JDK: JetBrains s.r.o. 21.0.8
Plugin version: 3.96.2-2025.2
Additional Info: None
Parent component:
com.intellij.openapi.wm.impl.IdeRootPane[,0,0,2560x1409,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 27 seconds
Sampled time: 17900ms, sampling rate: 100ms, GC time: 173ms (0%), Class loading: 0%, throwable=com.intellij.diagnostic.Freeze
at com.microsoft.azure.toolkit.lib.common.telemetry.AzureTelemetryClient.getClient(AzureTelemetryClient.java:176)
at com.microsoft.azure.toolkit.lib.common.telemetry.AzureTelemetryClient.trackEvent(AzureTelemetryClient.java:131)
at com.microsoft.azure.toolkit.lib.common.telemetry.AzureTelemetryClient.trackEvent(AzureTelemetryClient.java:119)
at com.microsoft.azure.toolkit.lib.common.telemetry.AzureTelemeter.log(AzureTelemeter.java:135)
at com.microsoft.azure.toolkit.lib.common.telemetry.AzureTelemeter.afterExit(AzureTelemeter.java:86)
at com.microsoft.azure.toolkit.lib.common.operation.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 locations in AzureTelemetryClient.java and AzureTelemeter.java, especially getClient, trackEvent, log, and afterExit. Reproduce or inspect the reported IntelliJ freeze and determine why this telemetry path blocks the EDT; done means the reported long freeze no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100