CodePudding user response:
Check code, with no objects created or release already nonexistent objectsCodePudding user response:
Install Eurekalog, see your memory leaks occur in whereCodePudding user response:
First call memory error check what reason, have memory calls error is stopped when debugging, if it is stopped are normal, if it is hardware errors also possible, change the memory bank or try hard diskCodePudding user response:
Memory error, is a serious cause mistake, can't skip, you have to find errors, correct code can run normally,A common mistake:
1, the array;
2, specify the statement pointer;
3, release the pointer to the memory of released;
4, pointer corresponding to the wrong type,