The test starts at the top, currently 400,000 json counts. If that test succeeds then it proceeds search upwards.

• Higher to 135000 - breaks server limit and hence your UA beats the test
• Lower to 45000 - you only need to go manually lower (not up) when the test fails
• Lower to 25000 - you only need to go manually lower (not up) when the test fails

Arguments

• l - length of test
• d - difference (if omitted, half of length), used in the "binary" search

Failure and you

When a UA runs out of memory all sorts of weirdness can result. However this test should fail by not moving higher (after an alert). In that case, you must manually choose the lower value. The lower value is suggested and hopefully loaded and displayed by your browser before the JSON download and parse test happens.

If you started the test and it didn't seem to do anything, I suggest you try lower to 45000 as a starting point. Good luck!

Comments on the public-mwts please. ~hendry

Source code

Memory test git