| Previous | Next |
| kOSKextReturnNoMemory | kOSKextReturnNotPrivileged |
kOSKextReturnNoResources
A loader resource other than memory is exhausted
kOSKextReturnNoResources is not a synonym for out-of-memory. XNU defines it for exhaustion of a resource other than memory and gives available load tags as an example. That distinction matters because adding memory does not address a collision or depletion in the loader’s own bookkeeping.
Use the return code to focus on the resource-lifecycle path: which operation retained a resource, whether an earlier load or unload left state outstanding, and whether the attempt occurs in a constrained boot or collection-processing context.
How it differs from nearby statuses
kOSKextReturnNoMemoryidentifies an allocation failure.kOSKextReturnInUseidentifies a loaded kext or outstanding references that block unload.kOSKextReturnCacheidentifies cache processing, without stating which resource caused the failure.
Evidence worth collecting
- The exact OSKext function or tool phase and the target bundle identifier.
- Load/unload history for the affected boot session and any prior failures that left a dependency only partially processed.
- The earliest detailed diagnostic naming the exhausted loader resource; the final status alone does not say which one it was.
References
Looking for a different code? Search another status or error code.