Hi,
The most common case for memory leak is there is a leak in the JavaScript code. Obviously to resolve such issues, you would need to fix the JavaScript code instead.
If you believe the leak is in the browser engine, then you can try to isolate the problem into a small test project and send the test project to us. We will debug into it and see what we can find. However we generally do
NOT try to fix the issue if it originates from the browser engine. This is because the browser engine is an extremely complicated piece of software, so for issues originates in the browser engine, we usually wait for the Chromium team to fix them first, and then port it to our product if possible.
Even if we usually do not fix issues in the browser engine, if you can provide a test project, we might be able to debug into it and provide some insight on what might have triggered and what could be done to avoid it. Thus a test project can still be helpful. See here for more information on how to send test project to us:
https://www.essentialobjects.com/forum/test_project.aspxThanks