Hello, I'm trying to fix memory allocation issues (leak/ live leak etc.) since using clang's leak sanitizer hasn't helped much. It seems that by clearing emscripten cache and compiling with --tracing flag, we can get a summary and details of allocations on a configured server. The project waywardmonkeys/emscripten-trace-collector: A server for working with emscripten's trace data. (github.com) <https://github.com/waywardmonkeys/emscripten-trace-collector> seems to be the server side component for this. However I see two issues here:
1) Minor nitpick: Documentation tells us to configure "http://127.0.0.1:5000"; however it seems we need an additional slash in the end ( ie. http://127.0.0.1:5000/ ) for it to work. 2) Last check-in was 7 years ago, and in the meantime, emscripten has changed. It seems it no longer sends JSON with 'static_top' and 'dynamic_base' params, and there are few other errors which cause exceptions for the python server. 3) I need to know the address (preferably symbolicated) of all big allocations (live leaks), it seems the client does send it but I couldn't find it on the server's website ( default: http://127.0.0.1:5000/ ) Can someone please point me in the right direction? I hope I don't have to recompile emscripten and change the trace collector to fix all the issues. Thanks, Sarang. -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAHqdETyX1-pGf4XHHgvMX2znEfTdjPw_8XCYXismPoh-fCRchQ%40mail.gmail.com.
