-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Obsidian Helper (Renderer).app crash on macOS 13.2 #11
Comments
Removing the visual studio error message image out of my vault allows the text extractor plugin to continue processing other images without crashing. I ended up with 788 .json files in the I then moved the problem image back into my vault at the original subfolder location. I expected Obsidian to crash but it didn't and appears to have processed the image successfully.
Additionally, I am able to find this image using Omnisearch after it is indexed: Now I'm confused why it crashed in the first place. |
The macOS update was probably a coincidence, but I can't explain why this particular file caused a crash (and then did not). At Obsidian startup, Text Extractor will output a log saying "X workers available", could you tell me how many workers does it have please? Your Obsidian installer version is also quite out of date I think, it's worth it to update it. You need to re-download Obsidian for that, it can't self-update. |
Updated the Obsidian macOS host app using Homebrew.
Startup LogsLooks like it's starting up 14 workers
|
I have the same problem.
I turned off this plugin to continue using Obsidian, but I would like to reanable it. |
Problem description
This week I upgraded my Mac Studio from macOS 13.1 to 13.2 and immediately my synced vault started being unusable. Non-synced vaults are functioning normally.
Behavior
When I open up my primary vault synced through Obsidian’s sync service, I can see my last note and interact with it for a few seconds. Then, suddenly the entire window goes blank. I can resize it but can’t move it around - there’s no top bar but there are the 3 macOS colored circle buttons in the upper left corner. Closing and reopening the vault gives me another few seconds to interact with the note before the window goes blank again.
I copied the vault to a new location (so that it's not being synced) and opening the new copy exhibits the same behavior.
In the system console I found evidence that the Obsidian Helper (Renderer).app is crashing. The main thread stack trace doesn't appear to be related to your plugin. I didn't include all the other threads since the crash report is huge so let me know if there are any specific worker thread details that would help.
Disabling the plugin prevents this crash. (See workaround below)
Crash report
https://forum.obsidian.md/t/obsidian-crashes-on-mac-after-update-on-every-few-seconds/52951/15?u=phatblat
Workaround
I was able to resolve the issue by manually deleting the Text Extractor cache located at
.obsidian/plugins/text-extractor/cache
in the vault folder and then reopening the vault. After some time the vault will stop rendering again, but purging the cache allowed me to disable the plugin and use Obsidian normally.With the plugin re-enabled and the cache freshly purged, I can watch it generate lots of .json under the
cache
subfolder. It looks like the plugin gets through a little over half of my images before it stops and the renderer crashes (561 .json files in.obsidian/plugins/text-extractor/cache/sc
).The last successfully written file is
2022-04-18 Monday Ditto Worklog-Screen Shot 2022-04-18 at 3.31.52 PM.png-5629be631531de426a2eccec772c94bd.json
It looks to me like it's been processing images in reverse chronological order, so this one would have been next.
Is there any way to see which image the plugin was working on when it crashed?
Environment
The text was updated successfully, but these errors were encountered: