ILJA SHEBALIN <[email protected]> wrote on Thu, 13 Apr 2017 at 18:52:07 -0400 in <[email protected]>:
> It was so strange that Growl for the first time caused Kernel > Panic. I judge this by seeing a line in the KP log which says that > BSD process attributing to the crash is...Growl. Here's it in all > entirety. Is it useful? The crash report does *not* say that Growl caused the kernel panic. The kernel panic occurred in the Nvidea graphics driver. Growl was the process that was executing at the time of the crash. There isn't reason to believe those two facts are related and it wasn't luck of the draw that Growl happened to be executing while the kernel crashed. Generally speaking, bugs in application code should be be able to cause the kernel to panic. Of course, any such things would be a kernel bug, and kernel bugs do indeed happen. But although all kernel panics represent kernel bugs, not all kernel bugs are because of userspace applications like Growl. I wouldn't put much stock in this being Growl-related unless it happens repeatedly and fingers Growl as the current process consistently. Even then, that is a necessary but not sufficient condition for it to be Growl's fault. [email protected] John Hawkinson -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/growldiscuss. For more options, visit https://groups.google.com/d/optout.
