Kernel Panics after updating to 3.6.0

joeliolio

I hate to point fingers, but I have been using Lion for a while now, and I think it's pretty stable (at least kernel-panic wise). I installed 1Password 3.6.0 today and have been using the new Safari plugin to update a bunch of my passwords. I have gotten 4 kernel panics in the last hour or so. The only apps that have been running is 1Password and Safari.



Obviously there could be many other things going on, but anybody else getting kernel panics? (This is where the screen gets grayed out from the top to bottom, then displays a message saying to hold the power button).

khad

Hello joeliolio,



Thanks for asking about this.



Most of us on the team are running Lion as our primary OS now and have been for some time. This is the first I have heard (inside or outside of the team) of any kernel panics due to 1Password (not just in Lion but ever). The only kernel panics I have seen in Lion are when restarting and/or shutting down my VMs in Parallels (due to hardware-related issues since the VM has access to it).



As you can imagine, we use 1Password quite a bit and have an extensive beta testing team as well. I'm not saying it is impossible that it is related to 1Password, but offhand I can't imagine how it would be. 1Password doesn't install or use any kexts (kernel extensions) and kernel panics are almost exclusively the result of OS level hardware issues. 1Password just isn't integrated into the OS in the way that device drivers [i]et cetera[/i] are.



Are you able to consistently reproduce the issue? I'd love to try to break things on my own machine. Heck, all of us on team like trying to break things. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />



Please let me know.



Thanks!

thightower

Are you running AV software, I have seen 1 panic reported for Integos's VB X6, on Apples forum. The OP just removed it till it was deemed compatible.



If it happens on a regular basis you could alway boot into safe mode and see if that will help you narrow down whats causing it. (Sincerely hoping its not 1P)