Memory Leak

[Chromo0511]

Environment

Onsen UI Version:

• 2.10.5
• 2.10.x

Framework:

• None

Framework binding:

• None

Additional libraries:

• None

Platform:

• Safari 12.0.1
• Chrome 70

Encountered problem

Memory leak on the navigator.
When you return to the previous page, a lot of components stay in memory.

How to reproduce

• Put this html file on your local machine,
• Do heap snapshot
• Click on "Push page 2"
• Click on the "Back button"
• Do another snapshot
• Compare the snapshot

You can repeat these operations many time, and the memory usage grow.

page-sample.html

Thanks for you help.

[wcmhc]

I can't seem to reproduce a memory leak with Chrome Version 68.0.3440.106 (Official Build) (64-bit), Chromium V8 6.8.275.26.

I used your exact code plus a small script addition to cycle in and out of Page 2 which resulted in a 3MB fluctuation in the heap that was garbage collected fairly regularly with a mass collection near the start of the profiling. The flat line at the end corresponds to Chrome opening the captured profile, hence the large spike in CPU (not sure why that portion is included in the profiling timeline, but it's there). The timeline shows 70 seconds (70000ms on the timeline) of running which means 70 cycles of pushing and popping the navigator. My tests used the heap profiling tool in Chrome.

Extra code:

<script>
setInterval(function() {
	myNavigator.pushPage('page1.html');
	setTimeout(function() {
		myNavigator.popPage();
	}, 500);
}, 1000);
</script>

Note: The 800+ errors are from the navigator being in a transition state when the next popPage() or pushPage(...) is called due to the timers being too short and are thrown by OnsenUI; they are not actual errors. Increase each timer by 2x for reduced errors. I simply want it to be more apparent

Are you able to point me to a specific portion of the heap snapshot, otherwise?

[Chromo0511]

If you look your JS Heap that grow. Very light because it's a very small content. But if you have a more big content is really more significant.
If you make comparaison between 2 snapshots, you can see a lot of nodes not released.

[github-actions]

This issue is stale because it has been open for 60 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

[github-actions]

This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.