Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Mac OS X > KERN_PROTECTION_FAILURE. What?

KERN_PROTECTION_FAILURE. What?
Thread Tools
Mac Elite
Join Date: Jan 2003
Status: Offline
Reply With Quote
Dec 1, 2003, 09:05 PM
 
This seems to be the only reason apps crash on my Mac these days, and I'm wondering what is causing it.

I get this vague memory from a long time ago that the work KERN was referencing to a bad font, or something or other.

Kern does mean this, right? And not kernel?


"Do I need to draw a diagram for you then to tell you that nerdy 16-17 year olds, fat chicks and old men turn my crank then? Will you understand it then or don't you follow still chris." - Landos Mustache
     
Mac Elite
Join Date: Jan 2001
Location: Saint-Jean-sur-Richelieu, Qu├ębec, Canada
Status: Offline
Reply With Quote
Dec 1, 2003, 09:53 PM
 
Originally posted by Misanthrope:
This seems to be the only reason apps crash on my Mac these days, and I'm wondering what is causing it.

I get this vague memory from a long time ago that the work KERN was referencing to a bad font, or something or other.

Kern does mean this, right? And not kernel?
In this case it's kernel. And what it means is that the kernel killed the task because it was trying to use a share of memory that it didn't have access to.
     
Mac Elite
Join Date: Feb 2001
Location: Washington, DC
Status: Offline
Reply With Quote
Dec 1, 2003, 10:09 PM
 
It's a very vague error, but it has to do with the way OS X manages memory.

Basically every app has to request memory from the kernel, and when some app tries to access a memory address that it doesn't own, the kernel detects this, and terminates the process.

Unfortunately, there are a lot of conditions that could make the app behave that way. And, while the kernel knows the program tried to access memory it didn't own, the kernel doesn't know why. There's really no way to track down the exact cause of the error, unless you have access to a binary with debugging symbols in it and the source code for the app.

It could be anything from sloppy programming to a bad font or preference file to bad ram. Like I said - vague error.
/Earth\ Mk\.\ I{2}/
     
Mac Elite
Join Date: Jan 2003
Status: Offline
Reply With Quote
Dec 1, 2003, 10:44 PM
 
BURN THE INFIDELS.

(thx)


"Do I need to draw a diagram for you then to tell you that nerdy 16-17 year olds, fat chicks and old men turn my crank then? Will you understand it then or don't you follow still chris." - Landos Mustache
     
Clinically Insane
Join Date: Oct 2001
Location: San Diego, CA, USA
Status: Offline
Reply With Quote
Dec 2, 2003, 03:26 AM
 
"Kerning" is a term used in reference to fonts (nothing to do with being bad -- it's just a property the font), but yes, in this particular case it's shorthand for "kernel."
Chuck
___
"Instead of either 'multi-talented' or 'multitalented' use 'bisexual'."
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -4. The time now is 02:44 AM.
All contents of these forums © 1995-2014 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.8 © 2000-2014, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2