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
@quyatong By default, {index: i} is not considered as memory leak by MemLab (it could be cache as your example app labeled). MemLab supports self-defined leak detector with the leakFilter callback.
You can start with marking all objects allocated as leak and then refine the leak detector based on your app:
I created a SPA. The code was written below.
scenario file:
I wonder how to define whether there are leaks, tks for your answer~
The text was updated successfully, but these errors were encountered: