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
Memory leak: Table, TableMeta and TableProperty classes are retained in memory after destruction when using table/column modifiers or column.getValueForRow#266
Closed
johanrd opened this issue
Apr 18, 2024
· 2 comments
Enter the index route and see that there is one instance of the Table class is retained in Heap memory. This is expected.
Exit the route and enter /testing (a route without a rendered table), then re-enter the index route. Now, see that the Table class retained in memory twice.
Repeat exiting and entering the same routes, and see that for each exit of the index route, new instances of the Table class are retained in memory:
Screen.Recording.2024-04-18.at.15.02.02.mov
This is also reproducible in my own webapp whenever I use a table or column modifier, or use the column.getValueForRow helper.
Removing all the modifiers and {{column.getValueForRow row}} from demo-a.md resolves the issue, so this is most likely caused by columns not being teared down correctly.
The text was updated successfully, but these errors were encountered:
there has been a memory leak in glimmer-vm around locally defined helpers and modifiers prior to ember-source 5.6 -- I believe if the docs app upgrades to ember-source 5.6+ the memory leak would be resolved
Table
class is retained in Heap memory. This is expected.Table
class retained in memory twice.Screen.Recording.2024-04-18.at.15.02.02.mov
This is also reproducible in my own webapp whenever I use a table or column modifier, or use the column.getValueForRow helper.
Removing all the modifiers and
{{column.getValueForRow row}}
from demo-a.md resolves the issue, so this is most likely caused by columns not being teared down correctly.The text was updated successfully, but these errors were encountered: