Skip to content

Memory leak, not calling VMMDLL_MemFree with the VMMDLL_Map_GetVadW call. #29

Description

@kweatherman

Not a big deal, but you call VMMDLL_Map_GetVadW without a matching VMMDLL_MemFree call.

Not sure how often get_memory_region gets called, but it will result in a memory leak each time.
If it's only called once not an issue since as we know all allocations get killed on process exit.

Just need to add a VMMDLL_MemFree before returning from get_memory_region().

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions