| Previous | Next |
| kOSMetaClassNoInit | kOSMetaClassNoDicts |
kOSMetaClassNoTempData
kOSMetaClassNoTempData indicates an allocation failure while the OSMetaClass runtime is collecting class metadata during kext registration. XNU uses temporary storage to stage metaclasses while the extension's C++ constructors run, so the failure belongs to the loader's registration transaction rather than to a normal I/O buffer supplied by an application.
A retry is not automatically meaningful. The same result can recur if the kernel is under pressure or if the registration sequence repeatedly reaches the same loader state. Capture the associated kext, class count, and preceding memory or loader diagnostics before deciding whether to retry or unload.
What helps distinguish the cause
- Correlate the result with kext loading and the class currently being registered.
- Look for memory-pressure, allocation, or OSKext diagnostics immediately before it.
- Separate temporary OSMetaClass staging memory from the driver's own DMA or user-buffer allocations.
- Avoid treating it as a recoverable client request failure without checking the loader state.
References
- Apple XNU: OSReturn.h
- Apple XNU: OSMetaClass.cpp
- Apple: deprecated kernel extensions and alternatives
Looking for a different code? Search another status or error code.