latest obsidian on mac os crashing like there is no tomorrow.
i am on sonoma 14.6.1 .
today obsidian wouldnt open any more.
keeps crashing whenever i open any file.
reinstalled, resynced, … doesnt matter … keeps crashing as soon as i open any file.
2 hours just not able to use obsidian and wondering if i should look for an alternative.
looking at the crash report it seems that Obsidian is crashing when trying to open a file from the vault. The key details are:
The crash occurs in the main thread (CrBrowserMain)
The exception type is EXC_BREAKPOINT (SIGTRAP)
The specific error message is:
-[__NSArrayM intValue]: unrecognized selector sent to instance 0x13003d94e00
vault is stored in ~/Documents/Obsidian
happens with synced vaults or when i create new vaults.
also got a info to delete .obsidian folder from the vaults and try again.
keeps crashing on me.
We haven’t released an update, so I am not sure what changed on your end to cause this.
If this happens when only the sandbox vault is running, it may be an OS problem or something else interfering. Do you run an antivirus or something similar?
hi @WhiteNoise , thanks for trying to help.
i eventually found the answer.
its crazy but in settings → extensions → added extensions LiquidText Actions UI cant be set to on. see screenshot
I can’t believe it, but I had EXACTLY the same problem – LiquidText (2.10.24) extension causing Obsidian (1.6.7) to crash hard when opening any note on MacOS Sonoma (14.6.1) – with or without plugins, on a fresh install of Obsidian, etc. (I even reinstalled MacOS from recovery…) But immediately upon deactivating the LiquidText extension, Obsidian returned to normal performance. THANK YOU for posting this. It would have taken hours and hours to walk backward to that recent (and apparently unrelated) change.
I registered to say a thank you that this just pinpointed the same issue for me after a week of frustration caused by LiquidText
Note that its blast radius is not limited to Obsidian but I also encountered crashes in Chrome and system apps. Their developer should issue a PSA and a fix asap.