Skip to content
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.

Sign up for GitHub

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

Jump to bottom

C Memory Leak #129

Open
olls opened this issue Jan 8, 2017 · 2 comments
Open

C Memory Leak #129

olls opened this issue Jan 8, 2017 · 2 comments
Labels
bug needs figuring out renderer
Milestone
C Renderer

Comments

@olls
Copy link
Member

olls commented Jan 8, 2017 •
edited by geraintwhite
Loading

There definitely seems to be a memory leak in the C renderer. After leaving it running for a few hours it slowed to a complete stop.
@olls olls added this to the C Renderer milestone Jan 8, 2017
@olls
Copy link
Member Author

olls commented Jan 24, 2017

This is definitely a problem

@olls
Copy link
Member Author

olls commented Dec 13, 2020

Could be caused by the ObjectsMap. It will malloc new Objects on a collision, which will probably happen when there are multiple mobs on screen, but it never free's them.

@olls olls closed this as completed Dec 13, 2020
@olls olls reopened this Dec 13, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug needs figuring out renderer
Projects
None yet
Milestone
C Renderer
Development

No branches or pull requests
1 participant
@olls