Brave indeed! I’m a software developer, and so I’m on a Big Sur machine used for testing our own apps. Now on stable release, not beta, but yes… I’m brave! haha. Maybe this can help improve the system for others as they upgrade.
(1 year old MacBookPro, 2.9Ghz Quad, 16 GB Ram – one of the better MBP’s you could buy at the time)
I did some poking around and noticed that Obsidian was using an enormous amount of RAM in my Application Monitor (2.2gb). That seemed odd to me. I quit the application and restarted it, and it instantly jumped up to the same memory usage.
I went spelunking a bit, and found that in my ~/Library/Application Support/obsidian/ObsidianCache directory were 3 json files. One looks to be application configuration, and 2 for each of my vaults. The json file for one of my vaults was just over 2gb in itself. (The actual vault content folder is only 1.7mb, 839 .md files, so this seems really odd).
I loaded up the json file in VIM and it appears to be the issue. This is the json file that corresponds to the vault in my screencast. It looks like somewhere something got stuck in an infinite loop and kept writing the same record for file “$ The Pyramid Principle.md” over and over and over until the file ends mid stream.
I’m not sure how I got into this state.
Either way, I quit Obsidian. Deleted that JSON file. Reopened that vault and saved a change. That regenerated the cache file, and it appears to be fine now (32kb). The laggyness appears to be fixed, it’s as snappy as it was a few weeks ago.
If I had to speculate, I’d say maybe Obsidian was chugging along trying to read that enormous JSON file, or perhaps whatever library was used to read the JSON file was struggling with it being invalid and at that size.
Consider my issue fixed, but I hope maybe my experience is helpful for the future.