@@ -2244,6 +2244,11 @@ <h2>Program Behavior</h2>
22442244</ul>
22452245</div>
22462246</dd>
2247+ <dt><tt class="docutils literal"><span class="pre">--js-memory-report=<yes|no></span></tt></dt>
2248+ <dd>Enable memory reporting for javascript scripts in the stats overlay.
2249+ This is disabled by default because it has an overhead and increases
2250+ memory usage. This option will only work if it is enabled before mpv is
2251+ started.</dd>
22472252<dt><tt class="docutils literal"><span class="pre">--load-stats-overlay=<yes|no></span></tt></dt>
22482253<dd>Enable the builtin script that shows useful playback information on a key
22492254binding (default: yes). By default, the <tt class="docutils literal">i</tt> key is used (<tt class="docutils literal">I</tt> to make
@@ -14350,8 +14355,8 @@ <h3>Internal stuff page</h3>
1435014355are missing.</p>
1435114356<p>Memory usage is approximate and does not reflect internal fragmentation.</p>
1435214357<p>JS scripts memory reporting is disabled by default because collecting the data
14353- at the JS side has an overhead. It can be enabled by exporting the env var
14354- <tt class="docutils literal">MPV_LEAK_REPORT=1</ tt> before starting mpv, and will increase JS memory usage .</p>
14358+ at the JS side has an overhead and will increase memory usage. It can be
14359+ enabled by setting the <tt class="docutils literal"><span class="pre">--js-memory-report</span></ tt> option before starting mpv.</p>
1435514360<p>If entries have <tt class="docutils literal">/time</tt> and <tt class="docutils literal">/cpu</tt> variants, the former gives the real time
1435614361(monotonic clock), while the latter the thread CPU time (only if the
1435714362corresponding pthread API works and is supported).</p>
0 commit comments