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

memory leak in game flow #16

Closed
dixx opened this issue Feb 11, 2014 · 6 comments
Closed

memory leak in game flow #16

dixx opened this issue Feb 11, 2014 · 6 comments
Assignees
@dixx
Labels
bug

Comments

@dixx
Copy link
Owner

dixx commented Feb 11, 2014

Steps to reproduce:

  • run compiled game, watch the memory it consumes
  • click repeatedly on "Fortsetzen", about 10 times
  • wait for 2 minutes

Actual behavior:
the memory consumption goes up and does not go down by itself

Expected behavior:
the memory consumption goes up and then goes down immediately, latest after 1 minute.
@dixx dixx added bug labels Feb 11, 2014
@dixx dixx self-assigned this Feb 11, 2014
@dixx dixx added wontfix and removed in progress labels Feb 11, 2014
@dixx
Copy link
Owner Author

dixx commented Feb 11, 2014

Did not wait long enough for Irrlicht garbage collector to start. Not a bug.
...
Irrlicht has no garbage collection!

@dixx dixx closed this as completed Feb 11, 2014
@dixx dixx added in progress and removed wontfix labels Feb 11, 2014
@dixx dixx reopened this Feb 11, 2014
@dixx
Copy link
Owner Author

dixx commented Feb 11, 2014

after inserting ObjectManager and such, the memory leak was clearly visible again. it is about 100MB atm.

@dixx
Copy link
Owner Author

dixx commented Feb 11, 2014

the meshes seem to remain in memory, and there is an additional texture added every time the game is loaded.

dixx added a commit that referenced this issue Feb 11, 2014
@dixx
free unused memory after game unloading, #16
373d29f
dixx added a commit that referenced this issue Feb 11, 2014
@dixx
remove unused texture after destruction, #16
919a8a9
@dixx
Copy link
Owner Author

dixx commented Feb 11, 2014

there are still 25MB memory leak every turn. Check Ground.cpp and the virutal file system.

@dixx dixx closed this as completed Feb 11, 2014
@dixx dixx reopened this Feb 11, 2014
@dixx
Copy link
Owner Author

dixx commented Feb 11, 2014

to check:

  • internal images
  • dynamic lights
  • virtual file system

@dixx dixx closed this as completed Feb 13, 2014
@dixx dixx reopened this Feb 13, 2014
dixx added a commit that referenced this issue Feb 13, 2014
@dixx
remove map tiles from world after game unload, #16
f67560c
dixx added a commit that referenced this issue Feb 13, 2014
@dixx
add class DebugStatistics, #16
1bc75ea
dixx added a commit that referenced this issue Feb 13, 2014
@dixx
shift memory cleanup from Ground to MapTiles, #16
eb031f7
dixx added a commit that referenced this issue Feb 13, 2014
@dixx
add memory cleanup method to Collision, #16
cca3f89
@dixx
Copy link
Owner Author

dixx commented Feb 13, 2014

the memory still leaks, somewhere in Ground, MapTiles or Collision.

dixx added a commit that referenced this issue Feb 16, 2014
@dixx
add Debugwindow to main menu state and game state, #16
d29ed61
dixx added a commit that referenced this issue Feb 16, 2014
@dixx
update memory cleaning, #16
788cac4
dixx referenced this issue Feb 17, 2014
@dixx
update texture handling to avoid memory leak
89b43a9
dixx referenced this issue Feb 18, 2014
@dixx
found the major memory leak in BasicStaticObject, while copying a mesh
4062a9c 
to be able to transform it independently of other occurences. The copy
is removed, but the original mesh is not for some reason. Investigate!
@dixx dixx mentioned this issue Feb 18, 2014
Closed
@dixx dixx closed this as completed Feb 18, 2014
@dixx dixx removed the in progress label Feb 18, 2014
dixx added a commit that referenced this issue Feb 20, 2014
@dixx
fix memory leak in static objects, #16
fc968f5
dixx added a commit that referenced this issue Feb 20, 2014
@dixx
fix memory leaks, Closes #16
de02f48
@dixx dixx removed the in progress label Dec 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dixx dixx

Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dixx