| Previous | Next |
| STATUS_CONFLICTING_ADDRESSES | STATUS_UNABLE_TO_FREE_VM |
STATUS_NOT_MAPPED_VIEW
The address does not identify a live mapped view
UnmapViewOfFile operates on the base address returned when the view was created. A pointer into the middle of the view, a private VirtualAlloc region, an already-unmapped address, or an address from another process does not identify that mapping. The section object can remain valid even after one view is removed.
Track the original view base separately from application pointers into the mapped data. Do not pass a rounded data pointer unless it exactly equals the returned base. Concurrent teardown should atomically transfer ownership so two threads cannot unmap the same view.
What to inspect
- Compare the address with the exact value returned by MapViewOfFile or the native mapping call.
- Use VirtualQuery to confirm the region type and allocation base before cleanup.
- Audit duplicate close and error-unwind paths for a second unmap.
References
- Microsoft: MapViewOfFile
- Microsoft: UnmapViewOfFile
- Microsoft: VirtualQuery
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.