Skip to content
This repository has been archived by the owner on May 10, 2024. It is now read-only.

Memory leak #1661

Open
aurodev opened this issue Oct 23, 2017 · 5 comments
Open

Memory leak #1661

aurodev opened this issue Oct 23, 2017 · 5 comments

Comments

@aurodev
Copy link

aurodev commented Oct 23, 2017

Atomic Editor and a fresh Racer 2D sample tested and show a slow memory leak that consumes around 3gb over a 5 hour period.

Another reference to a memory issue:
https://discourse.atomicgameengine.com/t/memory-leak-in-both-atomic-editor-and-atomic-player/461

System: Win8.1, AMD Fx 6350, 8gb, AMD Radeon HD 7700

@Alan-FGR
Copy link
Collaborator

That example is mine 😛

@aurodev
Copy link
Author

aurodev commented Oct 24, 2017

Nice example! Proc generation :)
Blank example, editor all leak. Profiling memory not really my area of "expertise". But I'm giving it a shot.
If I blindly stumble on it I'll be sure to report.

atomicmem1

@aurodev
Copy link
Author

aurodev commented Oct 24, 2017

(From a cmake gui generated project of Atomic)
b

@Alan-FGR
Copy link
Collaborator

Alan-FGR commented Oct 24, 2017

Nice example! Proc generation :)

@aurodev thank you 😄... it could be better though ;)
So apparently the problem isn't the example managed code. I'll try to reproduce that. Thanks for the info @aurodev

@aurodev
Copy link
Author

aurodev commented Oct 25, 2017

Ok, not conclusive but I built Atomic without ATOMIC_PROFILING and the memory leak seems to be gone. Let this Debug build sit for 2.5 hours still 78.1 MB. Diagnostics seemed to point to easy_profiler.
image

@Alan-FGR Alan-FGR removed their assignment Oct 25, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants