microsoft / microsoft/azure-tools-for-java

[IntelliJ] Uncaught Exception Freeze in EDT for 17 seconds Sampled time: 9500ms, sampling rate: 100ms, GC time: 113ms (0%), Class loading: 0% com.intellij.diagnostic.Freeze

Open
#11,483 0 comments 0 reactions 0 assignees View on GitHub

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.5 IU-252.28238.7
OS: Mac OS X
JDK: JetBrains s.r.o. 21.0.9
Plugin version: 3.96.3-2025.2
Additional Info: None
Parent component:

com.intellij.openapi.wm.impl.IdeRootPane[,0,0,1364x1005,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 17 seconds
Sampled time: 9500ms, sampling rate: 100ms, GC time: 113ms (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.AzureOpe

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the stack trace around AzureTelemetryClient.java, AzureTelemeter.java, and AzureOperation-related calls, then reproduce or profile the IntelliJ freeze if possible. Done means identifying the cause of the 17-second EDT block and verifying that the reported freeze no longer occurs.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.