Superset memory leak
See original GitHub issueA clear and concise description of what the bug is. After querying the same chart for a long time, the available memory continues to decrease until the system runs out of memory
Expected results
Recycle memory after querying the chart
Actual results
The available memory keeps decreasing
Screenshots
If applicable, add screenshots to help explain your problem. I started a scheduler job to query chart
How to reproduce the bug
1.force refresh of the chart in Dashboard 2. use memory profile 3. see log
After many times
use gc.collect() at end line, But the memory is not reclaimed
Environment
- superset version:
1.1.0
- python version:
3.7.9
- node.js version:
12.18.3
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (7 by maintainers)
Top Results From Across the Web
airbnb/superset - Gitter
@AnithaMurugesan I was just curious about what hardware specs you are running Superset on, things like RAM, CPU cores, etc. Things will be...
Read more >Preset Cloud — The Visualization Layer for the Modern Data ...
Preset provides a managed service of Apache Superset, an open source business intelligence software which Maxime Beauchemin started in at Airbnb ...
Read more >MemLab: An open source framework for finding JavaScript ...
We've open-sourced MemLab, a JavaScript memory testing framework that automates memory leak detection. Finding and addressing the root cause ...
Read more >How To Detect and Prevent Memory Leaks | Scout APM Blog
The above example is likely to cause a memory leak because the variable requests, which holds a new instance of the Map object,...
Read more >[GitHub] [incubator-superset] yamyamyuo commented on issue ...
[GitHub] [incubator-superset] yamyamyuo commented on issue #5930: superset memory leak? ... @vnnw thanks! it works! [ Full content available at: https://github.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for investigating this @chen-ABC ! I can try to repro and help get this fixed and released soon if this is indeed the culprit!
@zhaoyongjie
I think I found the cause of the memory leak.
memoized use tuple key , The keys for the same query are different. Because there’s an object in the key
I think we have the same problem in superset 1.3.0 example: