-
Notifications
You must be signed in to change notification settings - Fork 253
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory leak error and uses unit in Advanced demo, can point to component code error? #656
Comments
I also got this yesterday but with fewer errors. I didn't have time to investigate and it hinted at starting with a fresh pull. I will look again today. Update: This is strange. I went back to an old commit (Sep 6, full repository) and the problem still appears. This problem was not there when I had used the demo while making that commit. This is quite puzzling and doesn't make sense. Any ideas? |
Seems to be spurious and false error according to certain threads on google. I will ignore it for now unless someone gives more information in this thread on how to switch it off or diagnose further. |
This is the MadExcept report:
The second leak:
|
Reason is that the node-data is not explicitly allocated and deallocated (using Possible resolution could be to use objects instead of records, or to call Finalize() on the record. |
That's news to me. Thanks. But what I don't understand is, why am I seeing that message now. I didn't see it earlier. Has something changed in the demos or in the project settings? |
Yes, I turned on mem leak reporting: 2ae1d51 |
* Many of the forms were not using the event OnFreeNode to release node data.
Hello,
Testing with Advanced demo, first I recive and error in "System.ImageList" unit in GeneralAbilitiesDemo.pas, it is not a problem it is enought if I remove the unit, all works, but when I close the application it fires memory bugs, some times a lot of them.
Before I use this example and I did not recive this, the it is possible that the memory leak are in components?.
This images are from 2 executions
The text was updated successfully, but these errors were encountered: