Bug: Investigate potential memory issue with Legend Query
and Legend Taxonomy
#1092
Labels
Application: Query
Issues related to Legend Query application
Application: Taxonomy
Issues related to Legend Taxonomy application
Status: Needs Investigation
Studio Core Team
Opened by a member of the Studio core team
Type: Bug
Milestone
Similar issues
How are you using Studio?
Legend Query, Legend Taxonomy
Current and expected behavior
Legend Query
andLegend Taxonomy
there is a memory leak when rebuilding a new graph as we don't clear the old graph. Example a big dataspace, taking about ~450MB of memory. When this dataspace is picked memory went up to 450MB, when a new dataspace (smaller) was picked, the memory increased to around 650MB. The memory should decrease as we don't need the old graph as well. When the big dataspace is changed the memory size went above 1000 MB and caused a crash on chrome.Another thing to check is when we switch between graphs in legend query, how do we make sure to completely reset the graph?
This is part of the effort outlined in #927
This might potentially be under the same umbrella as #257
Steps to reproduce
No response
Model data
No response
Environment
Possible solution and workaround
No response
Contribution
The text was updated successfully, but these errors were encountered: