Why does the Safari debugger show ever-increasing memory usage?

 There's currently a problem in *Safari*'s own debugger, which causes it to display inaccurate JavaScript memory usage in the "Timelines" tab under "Memory" when data is transferred to WebWorkers. This incorrect measurement which seems to increase forever to impossible numbers can be safely ignored. instead, you can look at the actual "JavaScript Allocations" information in the same tab, showing stable low memory usage of a few megabytes. The Safari app's actual global memory usage can also be verified to be under control.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request