Comment 18 for bug 1174660

I totally understand.

This bug was filled in April and it was causing a big problem in our swift deployment. Since I applied the patch in July, the memory leak either is not happening in our deployment or it is not significant.

I'll be more than happy to apply a better patch but I'm afraid I can't find a better solution myself without help.