javascript RAM memory usage [duplicate]

Question

I have website which can upload images. I do CROP from client side before upload then in server side new optimize...

On Mobile devices when no Free RAM fails.

How I can get RAM memory usage from JavaScript to skip CROP if there no memory?

I am looking only JavaScript solution!.

PLEASE I do not have LEAK OF MEMORY!!!

if I open many apps and no much RAM left my strategy not working

I need CODE by JavaScript get the free RAM and if is it bellow some amount I skip the CROP

------------ OK define Fail: --------------

From mobile devices people take photo and upload it...
from JavaScript I perform CROP
1. around 2MB image goes to 300kb
2. I upload only 300kb then from server side 300kb --> 30kb that I save

If there is no RAM this FAILs

I do not want to say "try again"

I would like to Skip the CROP

Thank you very much for comments.
I handle the errors but I would like to avoid client to wait 40-60 sec and then message

If I go with NO CROP IS IT OK but saving near 1.7MB per image bandwidth... GREEDY :-)

window.performance good I will used thanks.
I will do research to have round trip from SERVER SIDE what I can do can I find it for Mobile devices

Answer 1

In Development

Use Chrome's DevTools for pretty comphrensive diagnostics. You can get JavaScript run-time diagnostics, request information, and basically anything you might need.

Client-side Testing

As far as testing how much RAM is available in your code itself, there isn't really a "correct" or "recommended" strategy (source). Obviously the best solution would be to just optimize your code; varying your site's display/interactions based of how many other apps a client is running could be confusing for the user (eg: they expect some tool to be displayed and it never is; they think the page isn't loading properly, so they leave; etc.).

Some highlights from the source above:

• "Counting DOM elements or document size might be a good estimation, but it could be quite inaccurate since it wouldn't include event binding, data(), plugins, and other in-memory data structures."

• You'll need to monitor both the DOM and the memory you're using for your code for accurate results.

• You could try using window.performance (source), but this isn't well-supported across different browsers.

Note: As Danny mentions in a comment below, showing an advisory message when a feature is disabled could clear up some confusion, but then why use the resources on a feature that is so optional that you could just not use it? Just my two cents... :)