| 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
| Record | Diagnostic value |
|---|---|
| requested allocation size if the callback exposes it | Locates the concrete message, allocation, module, or API boundary |
| process commit and address-space state | Separates payload-dependent behavior from build and process state |
| custom allocator identity and previous allocations | Makes the comparison reproducible without rewriting the original artifact |
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.
Keep the original bytes or object graph unchanged while testing reproduce with runtime default allocation. A change in process commit and address-space state after reload, plugin replacement, restart, or schema deployment is evidence about runtime state, not permission to discard the reproducer. When custom allocator identity and previous allocations points to one message, retain a cryptographic hash and the smallest safe sample instead of logging certificate, subscriber, credential, or private-key material.
Instrumentation
Record the full 32-bit HRESULT and lower OSS return number together with operation direction, symbolic PDU, encoding rule, byte count, and generated-table identifier. 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.
Decision matrix
| Controlled observation | Conclusion it supports |
|---|---|
| reproduce with runtime default allocation | A changed outcome isolates the first proposed control instead of a blind retry |
| requested allocation size if the callback exposes it differs between success and failure | The difference localizes the allocator could not satisfy an ASN.1 operation boundary before unrelated settings are changed |
| An independent decoder accepts the same artifact | Inspect generated schema, selected rules, ABI, and optional OSS modules before declaring the bytes invalid |
| A fresh control object changes the outcome | Investigate initialization, lifecycle, allocator ownership, configuration mutation, and concurrent access |
Completion check: the result
Bound untrusted sizes, correct allocator behavior, and verify both peak usage and successful cleanup. A recovery test built around reproduce with runtime default allocation should replay the same operation under the same schema and encoding rule, retain one deliberately invalid control, and verify ownership and cleanup after both outcomes. Success after an unexamined retry is not proof that requested allocation size if the callback exposes it now satisfies the codec contract.
Technical references
- Microsoft: OSS ASN.1 HRESULT definitions
- OSS Nokalva: encoder/decoder return codes
- OSS Nokalva: runtime functions and control initialization
- Relevant ASN.1 specification or runtime detail
Looking for a different code? Search another status or error code.