| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
fix: change the passed `View` to be a weak reference
…g to be used chore: add condition to check if weak ref has not been cleared when it is being used
|
test |
Sorry, something went wrong.
chore: add tracelogs
|
test |
Sorry, something went wrong.
|
test |
Sorry, something went wrong.
|
test |
Sorry, something went wrong.
|
test package_version#latest |
Sorry, something went wrong.
|
test package_version#latest |
Sorry, something went wrong.
|
test |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Checklist
What is the current behavior?
When navigating to a Page that contains any kind of elements (GridLayout, ListView, RadListView etc.), if you navigate back and trigger JS GC those elements and the Page itself are never collected and stay in the memory.

What is the new behavior?
When navigating to a Page that contains any kind of elements (GridLayout, ListView, RadListView etc.), if you navigate back and trigger JS GC those elements and the Page itself are collected and are removed from the memory.

Fixes/Implements/Closes #[Issue Number].
Here is a sample project that I created to test this case:
memory-test.zip