Inadvertently memory leaks: Try-catch (CException *e)

As far as possible to ensure the robustness of the code under the premise

One more layer of try-catch can actually handle some surprises.

But all CException-based exceptions cannot be directly delete

The following is the wrong way of writing

Try
{
	
}
catch (CException *e)
{
	delete e;
}

Originally thought that the exception object is not manually released (that is, do not delete)

But today found running n Days of server program memory usage increases

When debugging, we also find that the VS gives a memory leak hint

To know that CException has its own Delete method and needs to be manually invoked

Just like that.

Try
{
	
}
catch (CException *e)
{
	e->delete ();
}