Locating unfreed memory

Posted By: Aku_Aku

Locating unfreed memory - 06/29/20 18:12

At the end of acklog.txt I can see the following few lines.
Quote
Unfreed: 1122, CAT, 8 bytes
Unfreed: 1225, CAT, 12 bytes
Unfreed: 1294, CAT, 12 bytes
Unfreed: 1333, CAT, 12 bytes
Unfreed: 1410, CAT, 12 bytes
Unfreed: 1571, CAT, 12 bytes
Unfreed: 1586, CAT, 12 bytes
Unfreed: 1605, CAT, 8 bytes

What is CAT? How can I locate the memory addresses that aren't freed by the code?
Thanks in advance.
Posted By: Ayumi

Re: Locating unfreed memory - 07/01/20 14:21

I guess, you used sys_marker in your code (to localize unfreed memory) or your using of 3D Gamestudio functions is wrong.
Posted By: Aku_Aku

Re: Locating unfreed memory - 07/02/20 12:45

Yes, both of them are true smile

I am struggling with memory issues, I am considering to change the title of the topic.
Posted By: Dooley

Re: Locating unfreed memory - 07/02/20 14:39

sys_marker creates unfreeable memory?
Posted By: Aku_Aku

Re: Locating unfreed memory - 07/03/20 20:01

No, definitely doesn't.
Posted By: Superku

Re: Locating unfreed memory - 08/02/20 09:43

The engine sets markers itself. I sometimes come across them in acklogs. I think it's when you mess up memory related stuff. CAT could come from a str_cat instruction (str_cat may need to allocate new memory for a longer string).
The issue might be somewhere else though, because as you know memory issues are a pain.
Posted By: Aku_Aku

Re: Locating unfreed memory - 08/02/20 19:31

Thanks for everybody for the help. Luckily, I was able to eliminate the issue.
Special thanks for solving the meaning of CAT to Superku.
© 2024 lite-C Forums