Fix memory leaks in Geometry

[Russell Taylor]

Valgrind flags up quite a significant number...

[Russell Taylor]

(In [2685]) Clear some memory leaks in Kernel. Re #722.

[Russell Taylor]

(In [2702]) Remove some Geometry memory leaks (including ones just in tests). Re #722.

[Russell Taylor]

(In [2755]) Few more Geometry issues and some other tidying up. Re #722.

[Russell Taylor]

Remaining memory issues as of 31st July

[Russell Taylor]

The remaining issue is mainly around whether OpenCascade, through its internal memory manager, is holding onto a load of memory unnecessarily after its done its work. There's also something going on in ShapeFactory.

[Russell Taylor]

(In [3027]) Address some potential memory leaks in ShapeFactory. Re #722. (Also clear a couple of gcc compiler warnings.)

[Russell Taylor]

(In [3029]) Last plugging of a geometry leak for the time being... Re #722.

[Russell Taylor]

That's all the geometry memory leaks that are highlighted by running the tests, apart from the OpenCASCADE ones (see attached document). A couple of points about these:

• They may be spurious. OpenCASCADE has its own memory management (based on a pool-type implementation) that may not play nicely with valgrind.
• OpenCASCADE is only used if you don't already have a cached geometry (vtp) file - i.e. rarely.

[Stuart Campbell]

This ticket has been transferred to github issue ​1570