You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like after a certain point, the memory profiler begins to report allocated memory as "free," despite not actually showing that data as free in the numbered totals. It's possible this might not be a bug. In general, I think better explanations of what's going on with memory here might be needed.
You can see this in action by using this small app I built (repo) to allocate specified chunks of memory in wasm in megabytes.
The text was updated successfully, but these errors were encountered:
Version of emscripten/emsdk:
3.1.54
It seems like after a certain point, the memory profiler begins to report allocated memory as "free," despite not actually showing that data as free in the numbered totals. It's possible this might not be a bug. In general, I think better explanations of what's going on with memory here might be needed.
You can see this in action by using this small app I built (repo) to allocate specified chunks of memory in wasm in megabytes.
The text was updated successfully, but these errors were encountered: