@shrilola: Can you please be more specific about which tool do we need to use to get the memory usage report of the Farmville/Farmville2 game.

That will help us in further triaging of the issue.

Thanks,

@Sandeep: We have updated profiled scout file in google drive
https://drive.google.com/drive/folders/0ByAw0MvLVeI0OGNrNzFJOXN0d0U

You need scout app to open this flm file, you can download adobe scout from here.
http://www.adobe.com/in/products/scout.html

We have profiled a same level blob on Chrome 57 and 58 versions.
Here is our observations on 57 version
Total Memory used : 2256.233 MB
   Actionscript object memory: 1024.355 MB
   Bitmap : 414.488 MB
   ByteArrays: 427.849 MB
   SWF file: 41.37 MB
   Other(Network Buffers and some other overheads): 348.171

58 Version:

Total Memory used : 2399.86 MB
   Actionscript object memory: 1081.513 MB
   Bitmap : 447.66 MB
   ByteArrays: 451.684 MB
   SWF file: 41.37 MB
   Other(Network Buffers and some other overheads): 376.572

Looks like there is an increase in ByteArray and Bitmap memory.

Please let us know if you need any more details regarding this.

Deleted: Chrome 57 Version.png 53.2 KB

	Chrome 57 Version.png 53.2 KB View Download

Deleted: Chrome 58.png 60.0 KB

	Chrome 58.png 60.0 KB View Download

Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

We have also profiled memory on Chrome 58.0.3029.110 and we do see a spike in this version too.

This issue seems to be out of TE-scope. Hence, adding label TE-NeedsTriageHelp for further investigation.

Thanks...!!

Any update on this?

Hi,
We have created a test app to check the memory on different versions, we are consistently able to reproduce the issue on Chrome Version 58.0.3029.96 and above. 

Steps to reproduce the issue:

1. Load http://zlive-aws.s3.amazonaws.com/images/goat.html on Chrome version  57.0.2987.133 and 58.0.3029.96.
2. Open developer tool, check verbose log to get the memory. Take a reading of AmfTest Memory End.

Note: You have to enable flash to get the data.

On Chrome 57.0.2987.133 version total memory is 148115456 bytes (148.11 MB) and on Chrome 58.0.3029.96 version total memory is 186839040 bytes (186.83 MB). We are seeing around 38MB memory spike in a small app.

system details:

1. Google Chrome 57.0.2987.133 (Official Build) (64-bit)
Revision ec33cd0c06881d919ac0de419d829ad914e0be8f-refs/branch-heads/2987@{#887}
OS Windows 
JavaScript V8 5.7.492.71
Flash 25.0.0.148


2. Google Chrome 58.0.3029.96 (Official Build) (64-bit)
Revision 2a03c99a5f45c6d507af8eb2345ad68a565d1518-refs/branch-heads/3029@{#787}
OS Windows
JavaScript V8 5.8.283.37
Flash 25.0.0.148

Also attaching total game memory graph with this thread.

Deleted: Screen Shot 2017-05-18 at 5.19.17 PM.png 92.7 KB

	Screen Shot 2017-05-18 at 5.19.17 PM.png 92.7 KB View Download

lfg: Can you take a look? It seems like we have a reproducible Flash-related memory leak that occurs in a specific Chrome rev.

I tried to reproduce your testcase but I can't find any measurable difference between M57 and M58. I can get the 148/186MBs test cases on both versions, and they aren't consistent, likely due to garbage collection timings.

I strongly suspect that the numbers you are seeing from the clients are due to the fact that we migrated users to 64-bit from 32-bit starting with chrome 58. We only migrated users on 64-bit systems with >= 4GBs of RAM, and our internal data show that despite higher memory usage of the 64-bit version, we have fewer out-of-memory crashes due to having a larger address space.