breautek commented on issue #1498: URL: https://github.com/apache/cordova-android/issues/1498#issuecomment-1256250595
Not sure about any workarounds, especially since we don't know the cause but I'd be curious if native event listeners are cleared/reset. Such as the one that hooks a callback for the `deviceready` event, which I believe gets initialized regardless if there is a JS event listener or not. Reloading the entire application is generally what I do, but I don't have my projects configured in a way that I can simply edit the www sources and reload the webview to get them (e.g. no development server or using `cordova serve`, etc...). And I do understand the performance benefit of being able to do this, from a development speed perspective. I guess I do reload the webview sometimes when troubleshooting/debugging issues, but I've never ran into this memory leak, or at least to the point that it actually causes a OOM. Also note that the web inspector Memory tab includes memory consumed by the dev tools itself. So if you have persistent logging enabled so that console.logs are kept across reloads for example, constantly reloading will gradually increase memory. Same goes for persistent network information or keeping audits, etc. If you're finding yourself with very large console output that you're keeping around, I'd try clearing it, and once the JS garbage collector does it thing, you should see the memory usage get reflected in the Memory tab. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
