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
When the grid is reloaded in Chardonnay, (on library scan and when a book is "removed"), the DataGrid retains references to the old GridEntry objects so the GC cannot free them. This causes a pretty massive memory leak.
I'll need to do in chardonnay what classic already does: update existing GridEntry objects instead of instantiating new ones.
The text was updated successfully, but these errors were encountered:
Sorry, no. It's actually kind of involved. I took a massive shortcut when I made the main grid. I tried doing what you did in classic, calling BindToGrid to load the library on init and then using UpdateGrid to process changes, but I ran into a series of problems that are non-trivial to fix without causing the grid to flicker too much.
When the grid is reloaded in Chardonnay, (on library scan and when a book is "removed"), the DataGrid retains references to the old GridEntry objects so the GC cannot free them. This causes a pretty massive memory leak.
I'll need to do in chardonnay what classic already does: update existing GridEntry objects instead of instantiating new ones.
The text was updated successfully, but these errors were encountered: