https://bugs.kde.org/show_bug.cgi?id=357928
--- Comment #4 from Yuanyuan <y...@nd.edu> --- Yes, you are right. There are some Valgrind messages hiding among my output before that one, which are consistent with my findings when running the code. I have fixed them now. Thank you. But the problem in my main description still remains. I checked and found it happens when a function fails to returning 1. More specifically, when the function ends and a class should be destroyed, the pointer in that class cannot be deleted. My code for destroying the class is like the following: ~DerivativesII<Type>(){ if(df) delete []df; if(df2) delete []df2; } When I add some output sentence before and after the pointer-deleting sentence and run again, I found the program keeping deleting those two pointers many times. It's weird because I don't have a loop here. -- You are receiving this mail because: You are watching all bug changes.