disabled. It turns out that this generates a measurable amount of garbage per frame... partially due to a change I made elsewhere. It used to be that the frame values were never cleared unless the stats were displayed... thus the HashSets were always populated with the old frames' values. When I added a default app state to clear them every frame the hashsets regrow every time and generate ~1 meg of garbage every 15 seconds. Not a lot but unnecessary. I think this way is more explicit and we no longer rely on a side-effect. A related change will be checked in for the StatsView to properly enable/disable collection. git-svn-id: https://jmonkeyengine.googlecode.com/svn/trunk@10492 75d07b2b-3a1a-0410-a2c5-0572b91ccdca
Description
A complete 3D game development suite written purely in Java.
Languages
Java
95.4%
C++
2.5%
GLSL
1.5%
C
0.3%
HTML
0.2%