Linux memory leak / startup crash issue still exists in 7.2.5; troubleshooting + triage
I first experienced this problem with Zoom on Linux about three years ago -- as documented here and here (and perhaps more recently here but the description is inconclusive), trying to join a meeting will sometimes result in all available system memory rapidly filling with gigabytes of random data (over 50GB within about 30 seconds in my most recent case!) and eventually the system shuts down the Zoom app to recover the memory. I do join the meeting (other meeting participants can see my name show up), but usually can’t hear any audio or see the meeting window. Some common factors here:
- This problem doesn’t occur right away. I can usually have at least five successful meetings before it shows up. Once it shows up, the crash occurs every time I attempt to join a meeting until the problematic file is cleared (see below).
- The problem always shows up at the same point in the meeting flow: after clicking Join in the pre-join preview window (when I can set my mic / camera preferences) and before the main meeting window is fully rendered.
- I am on CachyOS, which is an Arch based distribution. I am using the newest version of Zoom packaged for Arch. However, this identical issue (same symptoms of rapid memory leak + crash, same pattern of onset) happened to me and many others on Linux Mint about three years ago, as described in the above linked forum posts.
Every time this has occurred, regardless of operating system, deleting the .zoom folder in the user’s home directory (with the app closed) and then trying to join the meeting again fully resolved the issue. I did some troubleshooting today to try to find out more specifically where the problem lies, and found that deleting local_dns_cache.db and local_dns_cache.db-journal in the $HOME/.zoom/data folder fixes it without needing to delete the rest of the folder, which is nice because user accounts and app preferences are retained. (I didn't pin down specifically whether it’s necessary to delete both the db and the journal file or whether one is sufficient, but will also troubleshoot this in the future.)
I have also reported this as a bug within the Zoom app, but didn’t have the opportunity to give this level of detail. If any of the devs are reading this, perhaps this can help with troubleshooting the root cause and releasing a fix.
For anyone else experiencing it, try deleting those specific files and see if it resolves the issue for a while. No need for root privileges since this is within the Home folder; this can be done with any file manager app if you show hidden files/folders.
Would welcome any other troubleshooting info -- thanks! I’m on an AMD system running up to date CachyOS on the default KDE Wayland session.
