Skip to content

Memory leak search #200

@andyleejordan

Description

@andyleejordan

I've been searching for the memory leak seen in #186 and #199 all weekend.

Here is a presentation of my latest search.

Spoiler: we need to search again, but please see the above for how we can track down this leak.

Here is the Git bisect log. Use git bisect reset and git bisect replay the-log to perform the search. Edit it to start at a different location in the search, as noted in the presentation.

My current prime suspect: as of #192 we are closing the sound threads which were the primary source of the memory leak, but I believe that the leak we have still pertains to the sound system. Are sound files being loaded but not closed?

Metadata

Metadata

Assignees

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions