UI freeze reports are now available in JetBrains Marketplace

JetBrains Marketplace now shows UI freeze reports attributed to your plugin in the Freezes tab on its management page.

I recorded a short walkthrough:

…along with a guide to setting up reporting and investigating freezes:

Similar reports are grouped into piles, with a representative report for each pile. Start with the short thread-dump excerpt, then inspect the full dump-N.txt samples captured every five seconds. JFR snapshots, stack analysis, and performance metrics may also be attached.

To enable Marketplace reporting, register the built-in handler in plugin.xml:

<extensions defaultExtensionNs="com.intellij">
  <errorHandler implementation="com.intellij.diagnostic.JetBrainsMarketplaceErrorReportSubmitter"/>
</extensions>

For Split Mode, register it in a frontend or shared module. Reports also depend on users submitting them or enabling automatic reporting, and on the IDE attributing the freeze to your plugin.

For analysis, open a full dump with Analyze Stack Trace or Thread Dump and trace what prevents the EDT from progressing. The guide also shows how to use Patrick Scheibe’s analyze-freeze skill, including guidance on coroutines and Dispatchers.Default starvation. Check the agent’s findings against the full dumps and your code.

Check your plugin’s Freezes tab. If a report leaves you stuck, share the IDE build, plugin version if known, relevant dumps, and what you’ve already checked in this topic.

This is great! I already see some freezes in our page, so I’m wondering if we need to add the marketplace reporting still. Are only a subset of freezes going to our page if we don’t have the errorHandler line?

@helinx You only see there freezes that IDE cannot attribute (mistakenly) to your plugin. If your plugin has no own errorHandler configured we definitely recommend using ours.

So it happens this way:

  • IDE detects a freeze
  • IDE uses heuristics that match thread dumps and attribute freeze to a plugin
  • If plugin has errorHandler it suggests users report freeze to plugin vendor, data goes to that errorHandler
  • If plugin has no errorHandler IDE only suggests users report freezes manually
  • If plugin cause is not identified the freeze data goes to JetBrains reporter

So it is better to explicitly enable JetBrainsMarketplaceErrorReportSubmitter so that you have diagnostics on Marketplace if you have no any.

Hello,
Can the two methods—automatic reporting and a custom implementation of ErrorReportSubmitter—coexist?

Errors are reported automatically only if error handler is JetBrains Marketplace. We are not allowed to submit data automatically to 3rd-party endpoints by data protection laws in many countries.

We registered com.intellij.diagnostic.JetBrainsMarketplaceErrorReportSubmitter as our plugin’s errorHandler (plugin xmlId com.db.database.tool, Marketplace id 19161, Databee). I submitted a plugin-attributed exception from the IDE Internal Errors dialog with Report to the Third-Party Plugin. The IDE accepted it: idea.log shows ITNProxy - report ID: 2115695489948323840 at 2026-10-29 14:41:27 (UTC+8). The Exceptions and Freezes tabs on the plugin management page are still empty (“We don’t have any data for your plugin”).

How long after a successful submit should a report appear on those tabs? Does the Exception Analyzer only show reports from Marketplace-installed, already-approved versions? This submit was from 2026.5.0 installed from disk; the latest published version is 2026.4.1.

I see everything has arrived to https://plugins.jetbrains.com/plugin/19161-databee-database-client--sql/edit/exception-analyzer

Usually it takes couple of hours for batch processing

Thanks! Where can I find the REST API documentation for that feature? It would be great if I could give the endpoint to my agent for analysis.