JetBrains announced on October 9, 2026 that UI freeze reports are now available in the JetBrains Marketplace. The feature ties UI stalls to specific plugins, helping developers identify when a plugin is the prime suspect in a non-responsive IDE.
To view these reports, developers should open their plugin’s management page and select the Freezes tab. A key caveat is that Marketplace reporting must be enabled in the plugin first.
HOW IT WORKS
Marketplace groups freeze reports by error type and accumulates similar reports into piles. Each pile presents a representative report to highlight recurring patterns without inspecting every occurrence. TechStaged has also covered Stripe Projects Brings “Vibe Deploying” Into a Single Developer Workflow.
The reports include an automatically generated thread-dump excerpt to orient investigation, and, where available, dump-N.txt files containing full thread dumps captured at five-second intervals. Additional artifacts may include report.txt and open-telemetry-metrics.csv for analysis and performance context.
GETTING STARTED WITH MARKETPLACE REPORTING
To enable Marketplace reporting for a plugin, register the built-in error reporting handler in plugin.xml. For plugins that support Split Mode, registration should occur in the appropriate module; a backend-only registration will not expose reports to the frontend.
Users can submit reports through the IDE’s error-reporting UI or enable automatic submission to JetBrains. If the Freezes tab shows no data, verify that the handler registration is in place and that the IDE identified the plugin as involved.
- Enable Marketplace reporting in your plugin (plugin.xml).
- Open your plugin’s management page and navigate to the Freezes tab to view reports.
- Submit or auto-submit diagnostic data via the IDE’s error-reporting UI.
- If the Freezes tab is empty, check the handler registration and report settings.
WHAT IT MEANS FOR DEVELOPERS
The feature provides a structured view of UI freeze data, including a representative sample per pattern and a starting point for debugging with thread-dump excerpts.
An example described by JetBrains notes a scenario where file I/O on the EDT is surfaced in a report, illustrating how analysis can point toward where the UI is blocked.
RELATED COVERAGE
- Stripe Projects Brings “Vibe Deploying” Into a Single Developer Workflow
- Deno Team Joins Cloudflare, Merging Workerd and Celld to Simplify Self-Hosting of Workers and Durable Objects
- Swift 6.4 debuts with default Swift Build in Swift Package Manager as Vapor 5 beta takes center stage
- GitLab rolls out organization-wide security risk dashboard in beta
- Developer Tools articles
SOURCES
- The JetBrains Blog: UI freeze reports are now available in JetBrains Marketplace Published · Primary source
