Closed loudoweb closed 9 years ago
Hi, can you describe your steps and when memory increased? For example, I know one case where a memory problem occurs:
1) open hxScout 2) open app under test (AUT) 3) close hxScout
If AUT doesn't crash, it begins collecting lots of memory, because the stats are being collected but no longer being flushed to hxScout. Also, if hxScout becomes paused or is too slow to keep up with AUT, you could perhaps get the same situation.
Can you determine (from the timestamps in hxScout) if hxScout is keeping up with the AUT? Is hxScout showing low framerate?
I will try to collect more information about this as soon as I can.
Uh oh, I think you might be right. I'll investigate further. Maybe the stats aren't being released properly, when while it's still running.
I've submitted a PR to hxcpp: https://github.com/HaxeFoundation/hxcpp/pull/272
You can access this fix now by grabbing my Debug.cpp file and placing it in your hxcpp/src/hx
folder.
That's for telemetry stats not being deleted properly. There's another fix in this hxtelemetry repo for the "memory collects after disconnecting" problem, pushing now.
Thanks!
Thanks. I'll tell you if I get more info on this.
FYI: This PR was merged into HaxeFoundation/hxcpp in git last night, and a nightly hxcpp build is available from: http://www.openfl.org/builds/hxcpp/hxcpp-3.1.39-432-g3845ba8.zip
Thanks again, Ludovic!
no problem. Thank you.
I found memory increase in my app when using hxScout. I believed that was a memory leak in my app but when I open my app without hxScout I do not have memory increase. I guess memory increase in hxScout is ok since it collects data all the time but why the memory used by my app is also increasing?