IntelliJ IDEA 2025.3 freezes on typing in sql file

This AI summary of 2 threaddumps, I can provide as a file if required.

Based on the provided thread dumps (threadDump-20251219-110035... and threadDump-20251219-110457...), your IntelliJ IDEA is freezing when editing an SQL file, and the dumps reveal several key symptoms and likely culprits:

🔍 Root Cause Indicators

1. Heavy activity around SQL file editors

Multiple coroutines and threads are tied to SQL files:

• EditorComposite(file=.../Query_51.sql)
• EditorComposite(file=.../debug_json_lane_events.sql)
• AsyncEditorLoader(file=Query_51.sql)

These indicate that editor loading and rendering for SQL files is active, but many associated coroutines are suspended and waiting on shared infrastructure.

2. Repeated use of FloatingCodeToolbarEditorCustomizer

Stack traces repeatedly show:

at com.intellij.ui.codeFloatingToolbar.FloatingCodeToolbarEditorCustomizer.execute(FloatingCodeToolbarEditorCustomizer.kt:28)
at com.intellij.openapi.fileEditor.impl.text.TextEditorImpl$2$1.invokeSuspend(TextEditorImpl.kt:102)

This suggests that every editor interaction (like typing) is triggering the floating toolbar logic—which may be blocking or slow due to heavy computation or synchronization.

✅ Known issue: In recent IntelliJ builds (especially 2024.3+ and EAPs like 2025.3), the Floating Code Toolbar has caused performance issues in large or complex files (including SQL).

3. Exodus database / JobProcessor contention

Many threads are stuck waiting on:

at jetbrains.exodus.core.execution.JobProcessorQueueAdapter.waitForJobs(...)
at java.util.concurrent.Semaphore.acquire(...)

This implies background database operations (possibly from Database Tools, AI features, or indexing) are blocking the UI because they’re not yielding properly or are overloaded.

4. AI/LLM-related coroutines are active and suspended

You have many coroutines from:

• com.intellij.ml.llm.nextEdits...
• Inline Edit Request Executor
• AIAssistantUpdateChecker

These are part of GitHub Copilot / AI Assistant integrations. If they’re slow or waiting on network/LLM responses, they can block editor responsiveness, especially if hooked into keystroke events.

5. No EDT (Event Dispatch Thread) stack visible – but “EDT freeze detector” is active

The EDT is likely blocked indirectly—not by direct long-running code on EDT, but by synchronized state or lock contention from background systems (e.g., PSI tree updates, highlighters, or toolbar rendering).