Ok, i have looked at the project and now i know where your impression
of a memory leak comes from. It is from the implementation of
Vector3f, which allocates and returns a new vector at every operation.
It is a very small amount, but then the memory usage grows very slowly
as well.

For performance reasons, the old vectors not any longer in use are not
being deleted. Depending on how much free memory the computer has, the
memory usage of a program will grow for a while, then stop at a
certain point. This is normal for current implementation. It is *not*
a memory leak.

I would argue that Vector3f should be made a struct.

I haven't investigated yet why the program crashes at exit, i'm up to
it yet. I'll rewrite the initialization and tell you then.

-eye