From 33744df48c6cb8c4f825d5d9f18e650ccc23940b Mon Sep 17 00:00:00 2001 From: Konstantin Nisht <36202647+knisht@users.noreply.github.com> Date: Wed, 26 Feb 2025 11:37:45 +0100 Subject: [PATCH] Document changes in threading contracts for 2025.1 (#1428) --- reference_guide/api_changes_list_2025.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/reference_guide/api_changes_list_2025.md b/reference_guide/api_changes_list_2025.md index 7bcfb2a2f..0f5e1db93 100644 --- a/reference_guide/api_changes_list_2025.md +++ b/reference_guide/api_changes_list_2025.md @@ -73,6 +73,11 @@ NOTE: Entries not starting with code quotes (`name`) can be added to document no ### IntelliJ Platform 2025.1 +The code scheduled with `SwingUtilities.invokeLater` and `SwingUtilities.invokeAndWait` does not hold the write-intent lock +: Consider using an explicit wrapping with `com.intellij.openapi.application.ReadAction.compute` or `com.intellij.openapi.application.WriteAction.run(com.intellij.util.ThrowableRunnable)`. + +Coroutines running under `Dispatchers.Main` do not hold the write-intent lock +: To restore the old behavior, consider using `Dispatchers.EDT`. ### Kotlin Plugin 2025.1