Okay, people REALY should learn what leaks are.
Leaks are objects in the memory, that you don't need anymore, take memory for sure and most times you lost access to them. In this case you're talking about leaks.
Locations don't leak if you use them again and again, they use memory yes, but thats just normal. They're called a leak in the moment you don't need them anymore, although nothing changed.
The same goes for your group. If you create it, it's stored somewhere in the memory and uses it, like normal stuff on the computer does. If you save it in the hashtable, the table just knows where to find the group in the memory. Loading it from the table does nothing else but saving the "place" where the group is to find, creates nothing new.
However, Slayer is somehow right. Although you're destroying the group, the hashtable still "points" to the spot in the memory, needs you to "remove" this too, but you're clearing the child table of the caster, so it's allright (at least I can't see anything from looking at it).
Group actions also DONT LEAK, only the group that's created in it leaks if you don't use a variable.
Set glaive_damagedGroup = (Load (Key dgrp) of (Key (Picked unit)) in glaiveTable)
Custom script: set udg_glaive_damagedGroup = CreateGroup()
Test Group
Events
Unit - A unit Starts the effect of an ability
Conditions
(Ability being cast) Equal to Divine Shield
Actions
Unit Group - Pick every unit in tempGroup and do (Actions)
Wait 3.00 seconds
Time - Every 1.00 seconds of game time
Game - Display to (All players) the text: (Name of (Picked unit))
