• Shaya Potter's avatar
    Fix memory leak when RM_Call's RUN_AS_USER fails (#12158) · 71e6abe4
    Shaya Potter authored
    previously the argv wasn't freed so would leak.  not a common case, but should be handled.
    
    Solution: move RUN_AS_USER setup and error exit to the right place.
    this way, when we do `goto cleanup` (instead of return) it'll automatically do the right thing (including autoMemoryAdd)
    Removed the user argument from moduleAllocTempClient (reverted to the state before 6e993a5d
    
    )
    Co-authored-by: default avatarOran Agra <oran@redislabs.com>
    71e6abe4
module.c 559 KB