Fork me on GitHub

for some reason, i can no longer open a project that has three modules as Deps projects. whenever i open it, i get the java.lang.IllegalStateException: ModifiableRootModelBridgeImpl was already committed or disposed and com.intellij.serviceContainer.AlreadyDisposedException: Already disposed: Module: '[NAME_REDACTED]' (disposed) followed by Unable to save settings: Failed to save settings. Please restart IntelliJ IDEA error and IntelliJ IDEA becomes totally unusable. has anybody else run into this? my environment:

IntelliJ IDEA 2021.1.2 (Ultimate Edition)
Build #IU-211.7442.40, built on May 31, 2021
Runtime version: 11.0.11+9-b1341.57 x86_64
VM: Dynamic Code Evolution 64-Bit Server VM by JetBrains s.r.o.
macOS 11.4
GC: ParNew, ConcurrentMarkSweep
Memory: 1979M
Cores: 12
Registry: scala.erase.compiler.process.jdk.once=false
Non-Bundled Plugins: String Manipulation (, com.cursiveclojure.cursive (1.10.3-eap1-2021.1), org.intellij.scala (2021.1.21)
Kotlin: 211-1.4.32-release-IJ7442.2


neither cache invalidation nor re-creating the project (i.e., deleting .idea directory, *.iml files) resolves this issue.


Hmm, no, I’m not sure what might be going on there. There have been changes in the latest IntelliJ versions to the ways that modules are synced, but I’ve not seen this one. Do you have a full stack trace in the log? Help | Show log in Finder/Explorer


Is this a project I can look at, or is it a work one?


i can send you the log file. unfortunately, this is a work-related project whose code i cannot share with you.


oh, actually, i was able to reproduce this problem with the following minimal, reproducible example (each of the modules only has an empty deps.edn):

❯ tree
├── idea.log
├── module_1
│   └── deps.edn
├── module_2
│   └── deps.edn
└── module_3
    └── deps.edn

3 directories, 4 files


i'm not sure if this is redundant now that we have a MRE but here is the truncated log file just in case.


Thanks, I’ve managed to reproduce the problem with that repo setup.


this is currently blocking us from working in this repo since there's no workaround either. when can we expect a fix to be released?


I’m not sure, I can do an EAP release as soon as I’ve identified the problem. Hopefully tomorrow.

thanks2 3

Ok, I’m still investigating this. It’s been reported a handful of times in the error tracker but it’s obviously a fairly rare corner case because it hasn’t come up much at all. However I’m almost certain that it’s due to a platform change (or possibly a bug) in IntelliJ 2021.1. So if you need a workaround tomorrow, my suggestion would be to try downgrading to 2020.3, I suspect that the bug will not be present there. I haven’t had a chance to try it myself though, sorry - it’s getting late here.

👍 2