Conversation
Same game as for bodies, just need to iterate over their list of fixtures.
|
what branch is it? From: Andrew Schwartzmeyer notifications@github.com Same game as for bodies like in #203#203, just need to iterate over their list of fixtures. As far as I can tell, we're not using joints, or we'd need to handle them too. @BIOEvolveTDhttps://github.com/BIOEvolveTD Try this on for size, it solves another significant portion of the memory leak. You can view, comment on, or merge this pull request online at: Commit Summary
File Changes
Patch Links:
Reply to this email directly or view it on GitHubhttps://github.com//pull/205. |
|
It is |
|
Generation 24, holding steady at 1.38 GB From: Andrew Schwartzmeyer notifications@github.com It is "fix-fixture-leaks." Reply to this email directly or view it on GitHubhttps://github.com//pull/205#issuecomment-93182615. |
|
Just cracked 50 generations for the first time. From: Andrew Schwartzmeyer notifications@github.com It is "fix-fixture-leaks." Reply to this email directly or view it on GitHubhttps://github.com//pull/205#issuecomment-93182615. |
|
Generation 70, holding at 1.53 Gb We're through the looking glass here, people.... From: Robison, Barrie (brobison@uidaho.edu) Generation 24, holding steady at 1.38 GB From: Andrew Schwartzmeyer notifications@github.com It is "fix-fixture-leaks." Reply to this email directly or view it on GitHubhttps://github.com//pull/205#issuecomment-93182615. |
|
Heck yes. I updated the Sway, I'm at 54 minutes, 90 generations, at less than 2 GB usage. I'll go ahead and merge this, and think we can proceed from here confidently. Users should be able to perform any necessary inheritance tests without running into issues. (I mean, there are still leaks, but it's good enough now!) |
Also fix leaks from fixtures
|
I'll be using joints soon, once I solve the appendage triangular representation puzzle. |
Same game as for bodies like in #203, just need to iterate over their list of fixtures.
As far as I can tell, we're not using joints, or we'd need to handle them too.
@BIOEvolveTD Try this on for size, it solves another significant portion of the memory leak.