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
So, JSon is a ridiculously inefficient format for stack traces - they can easily become very large. We may want to warn the user when they become too large, maybe a configurable limit. We should also try to use a more compact format, for example not using "name", "value" and "children", but rather "n", "v" and "c". The examples seem to indicate that it should be possible: https://github.com/spiermar/d3-flame-graph
The text was updated successfully, but these errors were encountered:
So, JSon is a ridiculously inefficient format for stack traces - they can easily become very large. We may want to warn the user when they become too large, maybe a configurable limit. We should also try to use a more compact format, for example not using "name", "value" and "children", but rather "n", "v" and "c". The examples seem to indicate that it should be possible:
https://github.com/spiermar/d3-flame-graph
The text was updated successfully, but these errors were encountered: