Orion has actually triggered two kernel panics for me in the past week. It's easy on battery life though, so I've been using it still when I'm on the go.
I'm not very familiar with this space, so perhaps someone could explain this to me. I was under the impression that a kernel panic indicates a problem at the kernel level, not in userland. Is it not the goal of most/all kernels to insulate themselves from userland mistakes?
I actually think it has something to do with webkit and the fact that I use Quartz Debug to disable vsync at all times. I'll try to repro, but anecdotally speaking, my M1 MacBook Pro restarted when I was doing something in the Orion browser and spit out the typical kernel panic "Send to Apple" dialog upon reboot.
It happens on Mac. It's when you get an infinite spinning beachball. Sometimes called beachball of death, but generally called kernel panic on Unix systems.
Most of the time with Macs it starts happening when you have hardware failure. It happens way more on Windows and Linux because of the much larger range of supported devices and drivers and the varying quality of the drivers for them. Most drivers running in Darwin as made by Apple. It's also the reason Microsoft created a certification program for device drivers for Windows.
I definitely had a corrupted CD-R backup that would kernel panic OS X, Windows 2000, and Linux, circa 2003.
Though, most of my OS X kernel panics were due to a GPU slowly going bad and randomly corrupting memory (both under OS X and Linux, when in a particular graphics mode).
QNX is the only OS that I've pushed hard and never seen a kernel panic. BeOS was nice in that my (userspace) ethernet driver would crash overnight most nights, and I'd wake up to a prompt saying "I'm going to restart the crashed driver? Okay?", but I could reliably kernel panic BeOS with some dodgy semaphore code in userspace.