sqldelight: Android Studio crashing after updating to 1.4.2
Build Environment SQLDelight version: 1.4.2 IDE version: Android Studio 4.0.1 Dialect: SQLite
I haven’t looked too much into it, but after updating the SqlDelight plugin to 1.4.2, Android Studio randomly started crashing (and taking a good chunk of my OS with it). I tried using Android Studio 4.1.0 RC 1 and it still happened. After downgrading the plugin to 1.3.0 the crash stopped happening.
Android Studio 4.0.1
Build #AI-193.6911.18.40.6626763, built on June 24, 2020
Runtime version: 1.8.0_242-release-1644-b3-6222593 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 5.7.1-050701-generic
GC: ParNew, ConcurrentMarkSweep
Memory: 4012M
Cores: 12
Registry: ide.new.welcome.screen.force=true, debugger.watches.in.variables=false, debugger.showTypes=false
Non-Bundled Plugins: Key Promoter X, org.jetbrains.kotlin, com.developerphil.adbidea, com.squareup.sqldelight, detekt
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 2
- Comments: 22 (11 by maintainers)
Given how critical this issue is, doesn’t it justify a quick 1.4.3 update on the stable channel to avoid more people being affected?
Thank you very much for the release with the fix, Alec! And of course, thanks to you and all the collaborators and contributors for SqlDelight.
if anyone runs into this before the next proper release you can download the snapshot plugin off our eap channel
Can confirm this happens as well when trying a goTo/FindUsages on AS & gradle plugin v4.0.1.
I also started getting this issue after updating the plugin. It appears to spawn hundreds of
javaprocesses upon using find usages.I just tried with 1.4.2 again and paid attention. It actually looks more like a memory leak, because all of my Chrome tabs, slack, etc… got killed.
I can consistently repro by performing a “Go to Declaration or Usages” action, and watch 10s of GBs of memory suddenly get used.