[SSSD] [PATCH] Tap a huge memory leak

[Simo Sorce]

The operations we use to deleted members in the memberof plugin are
quite inefficient, but on top of that we were also "leaking" a lot of
search results on the operations contexts, causing the runtime memory
footprint to grow immensely (as in gigabytes for a singe ldb_modify).

It was technically not a leak beacuase eventually all memory would be
reclaimed, but it was enough to make the OOM killer kill our processes.

After a deletion operation is finished, make sure to explicitly free
all the search results we do not need anymore, so that the footprint
remains low.

Simo.

-- 
Simo Sorce * Red Hat, Inc * New York