| Previous | Next |
| OSS_BAD_VERSION | OSS_PDU_MISMATCH |
OSS_OUT_MEMORY
OSS_OUT_MEMORY (0x80093008) is an OSS ASN.1 runtime result for allocator could not satisfy an ASN.1 operation. The runtime requested memory for output, intermediate state, or a decoded object and the active allocator returned failure. Because requested allocation size if the callback exposes it is central to this condition, Microsoft’s HRESULT range and the OSS Nokalva return-code documentation should be read together. Start the investigation by recording process commit and address-space state, then separate the encoded value from generated artifacts, call arguments, and the runtime package actually loaded by the process.
Where processing stopped
At the allocator could not satisfy an ASN.1 operation boundary, capture the first OSS function returning the value and note whether the operation was encode, decode, copy, compare, constraint validation, or trace setup. Preserve the selected PDU, encoding rules, and custom allocator identity and previous allocations; otherwise an outer certificate or security wrapper may hide the useful codec result behind a generic failure.
Isolation sequence
- Reproduce with runtime default allocation
- Apply a bounded message-size limit
- Check whether one malformed length causes an extreme request
Facts that change the conclusion
- requested allocation size if the callback exposes it
- process commit and address-space state
- custom allocator identity and previous allocations
Similar names, different faults: the result
MEM_ERROR denotes an invalid memory access; OUT_MEMORY is an allocation failure and should be investigated without assuming corruption.
Instrumentation
Where requested allocation size if the callback exposes it can expose sensitive content, a hash plus a bounded structural excerpt is safer than the complete payload. Use process commit and address-space state together with OSS module paths and versions logged once per process so packaging differences can be correlated without flooding normal diagnostics.
Completion check: the result
Bound untrusted sizes, correct allocator behavior, and verify both peak usage and successful cleanup.
Technical references
Looking for a different code? Search another status or error code.