Kernel Panic on macOS (crash, reboot)

@luckman212 : Thank you ! That’s pretty useful indeed as I never launched Obsidian from the terminal :innocent: !

I use and always have used the .theme-dark “Base theme” (so far) with translucent window on off.

As far as the CSS snippets go, I’ve got a few, but they are pretty common ones.

  • Styling the block quotes in Preview
  • Faint text when checkboxes are checked (instead of strikethrough)
  • Changed the font everywhere (Edit & Preview) + one specific mono font for codes
  • Changed the font-size of the footnotes (and references)
  • Changed the “flashing” highlight color when clicking on footnote/back ref.
  • Full color changes on the graph view
  • Changed the color of the ==highlighted text== (Edit & Preview)
  • Reduced the indentation in lists
  • Relationship lines for lists (Edit & Preview)

And that’s pretty much it :blush: .

Concerning the community plugins I use :

There was the very new TOC plugin, but I disabled it as I experienced a kernel panic while testing it (:confused:). The second kernel I run into yesterday was when trying to embed a TikTok video :laughing: .

As for the core plugins everything is enabled except :

  • Random note
  • Audio recorder
  • Workspaces
  • Publish & Sync

Not sure if any of this could help, but I didn’t run into any kernel panics today :grin: !

1 Like

Thanks for the thorough report. Hopefully we’ll discern a pattern sometime soon!

1 Like

This is all I’m hoping for too :blush: !
Thank you for trying @ryanjamurphy :blush: !

1 Like

Tried this yesterday evening, didn’t close obsidian over night and just had a crash and reboot.

I have a MacBook Air with M1 chip and I am on Obsidian v0.11 as well as MacOs 11.2.1. I use the Minimal theme, only a few snippets and a lot of plugins. I can share them if necessary.

Had 4th crash again on macos same details as before.
plugins :

  • advanced table
  • daily planner

using vim keybindings.
I don’t use graph view.
Theme :

  • red graphite

hardware :

  • macos big sur version 11.2
  • processor - 2.3 GHz 8-core intel core i9
  • memory - 32 GB 2667 Mhz DDR4
  • Graphics AMD radeon Pro 5500M 8 GB

NOTE : no custom CSS snippets

just giving some information so it’s easier for dev to track down the issue.

from now on i am keeping obsidian bare bones with no plugins and stock theme. Will report again if there is another crash.

2 Likes

Another one for me too here (2021-02-28 - 1:20 PM (UTC+1)).

Reported it to Apple (Just in case, I kept a copy of the report (same for the previous one too)) .

I didn’t have any yesterday (despite playing around with CSS Snippets and adding few plugins through Obsidian’s settings).

On the four kernel panics I encountered so far, 2 of them happened while adding external links to a note (between the copy of the link from Chrome but before being able to paste it in the note… in other words, while the link was still in my clipboard) :

  • When embedding the TikTok video (I was going to paste the link into an <iframe>)
  • And just now as I was formatting the markdown external link in my daily note ( []()) : It crashed while I was writing the text for the link [Foru] .

Each time I had just one single note open (solely in Edit mode).

No data loss so far and after reboot, Obsidian reopened exactly where it was left when the crash occured.
iCloud so far seems to be doing correctly its job :blush: .

As it’s the first time it happen in the past few days, I can say that :

  • I was able to add, update and or configure community plugins without crashes.
  • I’ve also been able to modify CSS snippets, test new ones (which I don’t use yet) and preview community themes without crashes, also.

But :

  • I didn’t do any “real” writings during those past few too (I’ve been in a procrastination phase :innocent: ), until now (even though it wasn’t much : just a tasks list of 94 words per Obsidian - 754 characters).

As for the rest, my Mac didn’t change in between my last post and now.

macOS Big Sur Version 11.2.1

MacBook Pro (Retina, 15-inch, Mid 2014)
Processor 2,5 GHz Quad-Core Intel Core i7
Memory 16 Go 1600 MHz DDR3 
Graphics Intel Iris Pro 1536 Mo
Hardware Overview:

  Model Name:	MacBook Pro
  Model Identifier:	MacBookPro11,2
  Processor Name:	Quad-Core Intel Core i7
  Processor Speed:	2,5 GHz
  Number of Processors:	1
  Total Number of Cores:	4
  L2 Cache (per Core):	256 Ko
  L3 Cache:	6 Mo
  Hyper-Threading Technology:	Enabled
  Memory:	16 Go
  System Firmware Version:	430.0.0.0.0
  SMC Version (system):	2.18f15

I’m still not using any community theme and to my previous list of my enabled community plugins :

I’ve added :

  • Recent files
  • Vault Changelog

And also re-enabled the Table of Content plugin which was just updated today.

For the core plugins, nothing changed. Everything is enabled except :

  • Random note
  • Audio recorder
  • Workspaces
  • Publish & Sync

I’m not sure I can be more precise than this here :blush: .


Edit : Yes, I can add one thing :

Just in case, I’ve run a diagnostic on my Mac (to put aside some hardware problem, as it’s pretty old and used :innocent: ) and it came back negative : there was nothing to see there, fortunately :blush: )

2 Likes

After starting Obsidian without gpu with this command

Terminal gives back this prompt quite often:

Obsidian Helper (Renderer)[1319:30798] CoreText note: Client requested name ".LucidaGrandeUI-Bold", it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:].

Maybe this helps

1 Like

Another one (4:45 PM (UTC+1))

This time I was playing with a CSS snippet concerning the relationship lines in Preview Mode, specifically :roll_eyes: .

I was trying to render relationship lines with lists containing different types of list (Bulleted list + Numbered list).

This lead me to discover that my CSS snippet concerning the relationship lines in Preview mode, literally break the scrolling when having a note open in Edit and Preview (with linked panes) at the same time :roll_eyes: .

I didn’t notice it before because I tend to scroll, when using linked panes while re-reading myself, in the activated Preview pane (rarely with my cursor in the Edit Pane) but today, for once, the activated pane was the Edit one and it looked like this (with the snippet still enabled) :

First with the Edit pane activated (which doesn’t works, as the preview pane jumps) and then with the Preview pane activated (which works)

And when I disabled the CSS snippet for the relationship lines in Preview mode, the scrolling trouble disappeared :

Yesterday, I thought there could be a relation between the kernel panics and my clipboard, today, thinking further, it just could be this scrolling trouble : I was in a task list when I tried to copy/paste my external link into my note yesterday and even if I didn’t have the preview opened at that moment, maybe this small bits of code was asking too much to the Obsidian Helper (Renderer) ? :woman_shrugging:

The CSS Snippet I used for my relationship lines comes from the Minimal Theme (and I have the same trouble of a jumping Preview pane when previewing the theme).

Well, I disabled the CSS Snippet for the relationship lines in Preview Mode (:cry:).

And as for the rest, it’s still the same except that there was an update of Big Sur so I’m now on macOS Big Sur Version 11.2.2.

1 Like

I just met another kernel panic.

My Environment :

MacBook Pro (13-inch, M1, 2020)
macOS Big Sur 11.2.1
Obsidian 11.4

I turned off the graph view in the Core plugin last week, I have never met any Kernel panic in the last five days. :smile:

Unfortunately, it happened after I switched the theme from Minimal to Atom.
(In my own experience, the reboot usually happened in a few hours after I changed the theme. )

Just giving some information.
Thank you~

1 Like

Did you have kernel panics with Minimal too?

1 Like

I did at least

1 Like

In my case, I didn’t have the Kernel panics with “Minimal”.

Actually, I used the “Pisum” theme and never changed the theme in the past few days and it’s fine.

Today, I used the “Minimal” for 4~6 hours then switched to “Atom”. (But I tried several different themes when I was switching the theme)
After a few hours, the kernel panic happened.

1 Like

Don’t forget to send the reports to Apple.

1 Like

I don’t use any theme, just CSS snippets, and one of them was from the Minimal theme.

I thought it was breaking the Preview pane when scrolling through lists but I could reproduce this with other themes too :woman_shrugging: while just previewing them…

There seem to be something wrong on that vault :roll_eyes:

As I created a new vault today, I’m going to work on this new one and see what happens :blush: . Maybe It’ll help debug the vault in which I encountered Kernel panics :woman_shrugging: .

Done, each time :blush: .

Is it useful to add a comment when sending the report ?
If yes, what should I say ? :innocent:

1 Like

not much other than emphasize that it’s caused by an electron app.

2 Likes

Thank you @WhiteNoise :blush: !

It’s basically what I did so far :wink: .

Is there any way to “symbolicate” these KPs to get a better idea of what’s leading up to the panic? It’s my (limited) understanding of kernel debugging that without this symbolication, the stack traces are basically worthless.

To be honest, if i could dig into the reports, I would do it just out of curiosity :blush: .

Looking on the web about kernel panics and falling into a very small rabbit hole, I ended up opening the Console on my Mac for the very first time :innocent: .

In the system logs, I’ve found this :

Mar  2 18:53:08 NameOfMyMac Obsidian Helper (GPU)[5861]: getattrlist failed for /System/Library/Frameworks/OpenGL.framework/Resources//GLRendererFloat.bundle/GLRendererFloat: #2: No such file or directory

The time is basically when I opened Obsidian. No idea what it means though :woman_shrugging: .

After 3 days without a kernel panic, I just got one this afternoon as I was working on a very new vault (reported to Apple).

As it’s a new vault (iCloud - 74 Ko - 50 files in 7 folders) it means that :

  • No community theme/plugins are enabled
  • No CSS snippets have been added yet

As for the Core plugins, everything is enabled except :

  • Random note
  • Slides
  • Audio recorder
  • Workspaces
  • Publish & Sync

For the 3rd time though, the kernel panic happened while I was trying to copy/paste something from Chrome into a note in Obsidian.

I had 2 different notes opened side by side, both in Edit mode.
One was a list (some type of Index) and the other was a note concerning one of the items in the list. I was going back and forth (Cmd + Tab) between Obsidian and Chrome to complete my note copying and pasting what I needed.
I had done this for quite a few hours when, wanting to paste what I just copied from Chrome, I tried to place the cursor at the right place in my note but Obsidian froze (for few short seconds) and the kernel panic happened.

As for the rest :

Obsidian v0.11.3
macOS Big Sur Version 11.2.2
MacBook Pro (Retina, 15-inch, Mid 2014)
Processor 2,5 GHz Quad-Core Intel Core i7
Memory 16 Go 1600 MHz DDR3 
Graphics Intel Iris Pro 1536 Mo

@Pch Your post rang a bell for me. I remember pretty clearly that my KPs also seemed to happen when copy/pasting. That could be an important clue! I haven’t had a panic in a couple of weeks (knock wood) but I will keep a closer eye on this.

As per my previous post, I still think we are lost without the symbol (dSYM) files to be able to decode the crash dump. And we’re fooling ourselves if we expect Apple to help on this. It’s going to have to be fixed by the Electron devs somehow.

It baffles me that such a low level crash occurs in such a high-level app like Obsidian. Especially since VSCode is also written in Electron, supports 1000x the amount of plugins, and is used my millions of people every day…and seems to not suffer from this somehow. So strange…