-
Notifications
You must be signed in to change notification settings - Fork 19.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] dynamic data & time axis without showSymbol memory leak #19984
Comments
correct observation, can confirm.
A progress table of usedJSHeapSize change after 180 (20*9) updates.
However jsHeapSizeLimit is 2,172,649,472 and GC moves in mysterious ways, so I'm not sure if this is a real problem... |
See related comment / screenshot of JS heap snapshots that I took before my browser tab eventually crashed: #20022 (comment) |
It seems there was a recent fix related to this! #20161 @plainheart can you confirm, looks like it’ll be in the next ECharts release? |
Pulled in the nightly release with the fix from #20161 and the issue is still present. Browser tab crashes when there are many series with symbols |
@JessonLiou Please check if this issue persists in v5.6.0 and file a new issue if it does. |
Closing this issue since I think this has been fixed in v5.6.0. (#20161) |
Version
5.5.0
Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html?c=dynamic-data2&code=GYVwdgxgLglg9mABAJwIZgCZwLYBFVSoAUAlIgN4BQiiYcA7ogLy0Cmj-UrRA1HYz0QJW-AJ4kA3NUQA3VABsQrZrIVLEggLIEAFgDo0mHKUQAqRACYAjIgC0iKwAYpNZKyghkSKjRphU2KwAXLQMelBwAMpQyDBgAOakADTSNHKKwYgA2qm-Wfx68e4AYiDy8gCarKjIyaH0he6aCFA6JoJWSfWNUJzcJAC6egBWcHFEAOQA9BMkKb6-2q0GcOAYROlKJLkD0gC-UnuU8u6IGASoKlkDUidQ9Spg7Ih9RFYAnO8A7F3vXQDMkmOp2EYhUFgALGZEP8AGyORzQpwI26nTbKFhLfSGLDYEzmZHOSjAODIRAbGqIGAqZxUxAAHgcCNpMB4PDIPjOFz0AAcQABnNo4nCcYgkIFHOA82AIFSc2BQE4hTk0LgADygIQmuFE_mwMAgLwuiAAZIgACowQKIACCapg_Im-3miAicHksB5ytyMRg8SKyC1qHtjpdNBJyGwBC4gcQoEgMqQRB5NQC_I5uRoKbQ2H5KmzaayjhumdUZPOXEez1eBdzej1rCBC1c7k8SdLNArrB6rzIPA7iGmEw0A6IXZ6zTArXaDj7A6HI-bvnHRSgpXKVRq7XniC1i6XiFr_L06KyVl2S6bvj2YcQwYdAAUxlPWLGVb50FaCPAwCFgAp-VYXIjhoG9pDVO0HW9BYoFEHlMgmWBAgmW9-R5eQYCgAAZOJMnfGhBQYP8AKAhYQMQMCaFESD-Wg3xYPgrV0RQ3IACNVkwGpRAAcVQL1skcLoJmRABSCYBlQ9DMJwp46IWQj6GI-RAOA51pEA2JWFo7Jcnw2gAgQ4pUAAa2UUUWKXBiEIwp4LObKYpkQBTIlEbB2PkJTANvTsLhCCtUFUmhdgOShAKgABJF9kHSIh42gH9yQzcNSXJOQyWpFgWQZBwAFYWTZJLl25QUYGAKBSBcIrCF5AUhXQXFRVIK9yOwUQAGEdBqKA9DCgB5aUfyId8NJgLSQhyJc9J8wg_IuUtyKC_YJS6QlJCAA
Steps to Reproduce
Current Behavior
memory rised
Expected Behavior
memory not rise
Environment
Any additional comments?
Related issues: #7125, #18865
The text was updated successfully, but these errors were encountered: