Replies: 3 comments
-
I would like to see all this stuff in a different page instead of seeing it below the canvas. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I don't think there has been any work done on the memory profiler in a long time. I you would like to work on it, or figure out a way to make it extensible perhaps, that would be great! |
Beta Was this translation helpful? Give feedback.
0 replies
-
Sure I'd love to improve it. Right now, I'm working on other things, but I expect to be back on wasm stuff in a month or two. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When the link flag
--memoryprofiler
is used,library_memoryprofiler.js
inserts itself as adiv
element in the main html. This div does not have an id or class and is very hard to find when the canvas is declared withposition: absolute
or it is embeded in a react or vue component. Is it possible to somehow print the allocation information in the dev console or maybe serve the memory allocation map in a different url for convenience?Beta Was this translation helpful? Give feedback.
All reactions