MemLab cannot analyze heap across page reloads about memlab HOT 2 CLOSED

@applesaucesome MemLab test scenario (with action and back callback) finds memory leaks by diffing heap snapshots. If the web page reloads, diffing heap snapshot doesn't make sense since browser refreshes the JS heap.

Have you tried the cookies callback?

We may be able to support start checking reload after the setup call so you can do the login with reloading inside the setup callback.

MemLab also supports finding memory leaks based on a single heap snapshot taken manually from Chrome.

memlab view-heap --snapshot <path to .heapsnapshot file>

from memlab.

@JacksonGL I'll give these alternate approaches a try, thank you!! Also, I support the idea of being able to pick when the check starts, like you're suggesting. I think it could be a more flexible approach for these login/redirect scenarios.

from memlab.