879031 - [browser] Possible memory leak in gaia browser

Status: RESOLVED DUPLICATE of bug 879756

(Firefox OS Graveyard :: Gaia::Browser, defect)

Description

[Robert Wood [:rwood]]

Attachment: About_memory logs

It looks like there might be a memory leak with the browser on Firefox OS.

Found by running a gaia-ui endurance test (browser_wifi) on inari, on b2g 18 v1.0.1. The test starts up the browser, navigates to a URL, verifies the page is displayed, then closes the browser, then repeats. The test is ran 100 iterations, and every 10 iterations there is a device-side checkpoint that records the b2g memory use value.

To demonstrate, click on any of these datapoints on DataZilla one the graph at the following link.  This is from the browser_wifi test running on inari with b2g v1.0.1:

https://datazilla.mozilla.org/b2g/?branch=master&device=inari&range=7&test=endurance_browser_wifi&app_list=browser&app=browser&gaia_rev=9b3309b9e488d835&gecko_rev=3501b06c9fc382a6

You will notice on the detailed data in the chart at the bottom, that for each b2g memory checkpoint (every 10 iterations), the memory use increases. I did not expect the memory use to increase, especially when the test is always browsing to the same URL each time.

The source code for the browser_wifi test can be found here:

https://github.com/rwood-moz/gaia-ui-tests/blob/gaiastress/gaiatest/tests/endurance/test_endurance_browser_wifi.py

I also did a mozilla-central build of inari with DMD enabled (June 3). Attached are about_memory logs before, and then after running the same browser_wifi test at 100 iterations. Attached is also the corresponding b2g memory process data output from the endurance test.

Comment 1

[Robert Wood [:rwood]]

Attachment: Endurance test b2g memory data

Inari b2g process memory checkpoint data from the browser_wifi test, mozilla-central build jun3

Comment 2

[Robert Wood [:rwood]]

Correction: The about_memory logs are for an Inari build of v1-train not mozilla central

Comment 3

[Robert Wood [:rwood]]

This might be the same as Bug 879756... which also closes the app under test between iterations - perhaps it is an issue with closing an app  or cards view, and not the particular app itself...

Comment 4

[Ben Francis [:benfrancis]]

I'm not sure where to start diagnosing this, but please reopen if it turns out this is specific to the browser app and not the more general case described in bug 879756