Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Memory measurement is broken

See original GitHub issue

Output looks currently like that since updating to Chrome 73 and returns way too high values:

*** memory 2.9918212890625
*** memory 4.30865478515625
*** memory 5.489418029785156
*** memory 6.524208068847656
*** memory 7.559226989746094
*** memory 8.594490051269531
*** memory 9.6324462890625
*** memory 10.673210144042969
*** memory 11.708724975585938
*** memory 12.743614196777344

(Chrome 72 reported quite constant values close to the first reported value)

Issue Analytics

State:
Created 4 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

krausestcommented, Mar 24, 2019

As for 1: If I force GC before window.performance.memory.usedJSHeapSize results are closer. And I found that I measured window.performance.memory.usedJSHeapSize after afterBenchmark and benchmark 21 performs some action there. So now the two metrics are very close for chrome 72:

Chrome 72:
Benchmark 21:
Results for memory [ [ 1.6121673583984375, 1.645843505859375 ],
  [ 1.6677169799804688, 1.6966323852539062 ],
  [ 1.6679458618164062, 1.6968612670898438 ],
  [ 1.6653823852539062, 1.6942977905273438 ],
  [ 1.665771484375, 1.6946868896484375 ],
  [ 1.665771484375, 1.6946868896484375 ],
  [ 1.6663589477539062, 1.6952743530273438 ],
  [ 1.6663589477539062, 1.7135696411132812 ],
  [ 1.672454833984375, 1.7013702392578125 ],
  [ 1.672454833984375, 1.7013702392578125 ] ]

Benchmark 22:
Results for memory [ [ 1.8744125366210938, 1.8979568481445312 ],
  [ 2.0248565673828125, 2.048370361328125 ],
  [ 2.0250701904296875, 2.048583984375 ],
  [ 2.0229949951171875, 2.0465087890625 ],
  [ 2.0231246948242188, 2.0466079711914062 ],
  [ 2.0233840942382812, 2.0468673706054688 ],
  [ 2.0238723754882812, 2.0473861694335938 ],
  [ 2.0299835205078125, 2.053497314453125 ],
  [ 2.0298995971679688, 2.0534133911132812 ],
  [ 2.0300674438476562, 2.0535812377929688 ] ]

Benchmark 23:
Results for memory [ [ 2.1467132568359375, 2.1707839965820312 ],
  [ 2.16314697265625, 2.1866607666015625 ],
  [ 2.1609039306640625, 2.183868408203125 ],
  [ 2.2953109741210938, 2.3182754516601562 ],
  [ 2.2955474853515625, 2.3202743530273438 ],
  [ 2.295989990234375, 2.3189544677734375 ],
  [ 2.2960357666015625, 2.319000244140625 ],
  [ 2.3031539916992188, 2.3261184692382812 ],
  [ 2.3029632568359375, 2.325927734375 ],
  [ 2.3032989501953125, 2.326263427734375 ] ]

Benchmark 24:
Results for memory [ [ 2.53228759765625, 2.55609130859375 ],
  [ 2.5386886596679688, 2.562286376953125 ],
  [ 2.3926010131835938, 2.4173736572265625 ],
  [ 2.3931045532226562, 2.4167022705078125 ],
  [ 2.538299560546875, 2.5618972778320312 ],
  [ 2.538604736328125, 2.5622024536132812 ],
  [ 2.5386886596679688, 2.562286376953125 ],
  [ 2.545654296875, 2.5692520141601562 ],
  [ 2.5455703735351562, 2.5691680908203125 ],
  [ 2.545440673828125, 2.5690383911132812 ] ]

Benchmark 25:
  [ 2.2166366577148438, 2.237396240234375 ],
  [ 2.2160568237304688, 2.23956298828125 ],
  [ 2.2160263061523438, 2.2401199340820312 ],
  [ 2.216583251953125, 2.2400894165039062 ],
  [ 2.216583251953125, 2.2400894165039062 ],
  [ 2.2174606323242188, 2.240966796875 ],
  [ 2.2235565185546875, 2.2470626831054688 ],
  [ 2.2235565185546875, 2.2470626831054688 ],
  [ 2.2248764038085938, 2.248382568359375 ] ]

0reactions

ryansolidcommented, Mar 27, 2019

Yeah those numbers are much better. Things are still different in certain areas but at least relatively frameworks are comparably where they were before. I look forward to when Chrome fixes whatever the issue is.

Top Results From Across the Web

How to test RAM and find errors | Rock Paper Shotgun

Step 1: Open Windows Memory Diagnostic by searching for it in the Start menu's search bar. Then, click “Restart now and check for...

Data Rescue Series (Part 2): How to deal with broken memory ...

Overheating of the memory card causing several and very unique errors. Mechanical damages that cause broken solder connections inside the ...

Classification of Working Memory Loads via Assessing Broken ...

In conclusion, our findings provide an advanced framework to accurately classify various levels of working memory with the broken detailed balance of human ......

How to Fix Your Broken Perception of Time - Zapier

To fix our broken perception of time, we can reevaluate our ... Last but not least, our memory is both cause and effect...

Memory of a Broken Dimension may melt your eyes, brain

Essentially Memory of a Broken Dimension is comprised of two parts: a computer terminal where players must input codes into an esoteric ......