microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception Freeze for 25 seconds Sampled time: 8000ms, sampling rate: 100ms, GC time: 692ms (3%), Class loading: 0%, CPU load: 6% 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 IC-251.23774.435
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,0,1386x865,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 for 25 seconds
Sampled time: 8000ms, sampling rate: 100ms, GC time: 692ms (3%), Class loading: 0%, CPU load: 6%, 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.microso
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 at AzureTelemetryClient.java, especially getClient at line 176, then follow trackEvent into AzureTelemeter.java and its afterExit path. Reproduce the 25-second IntelliJ freeze on the reported Windows 11, JDK 21, and plugin versions, then verify that this telemetry flow no longer freezes the IDE.
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
- 30/100