[doc] Fix a typo in debugging_memory_issues.md

Tbr: erikchen@chromium.org
Bug: 801006
Change-Id: I177ad5a127c2ff5e17b0d036351fe735f862b173
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2437436
Reviewed-by: Egor Pasko <pasko@chromium.org>
Commit-Queue: Egor Pasko <pasko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#811720}

This commit is contained in:

Egor Pasko

2020-09-29 15:32:24 +00:00

committed by

Commit Bot

parent 9b3041c034

commit a60f30f2a7

1 changed files with 1 additions and 1 deletions

									
										2

docs/memory/debugging_memory_issues.md
									
				@ -78,7 +78,7 @@ link](/docs/memory/investigating_heap_dump_example.md).

				  This interface surfaces all available information, but can be overwhelming and

				  is usually unnecessary for investigating heap dumps.

				    * Important note: Heap profiling in the field uses

				      [poison process sampling](https://bugs.chromium.org/p/chromium/issues/detail?id=810748)

				      [Poisson process sampling](https://bugs.chromium.org/p/chromium/issues/detail?id=810748)

				      with a rate parameter of 10000. This means that for large/frequent allocations

				      [e.g. >100 MB], the noise will be quite small [much less than 1%]. But

				      there is noise so counts will not be exact.

[doc] Fix a typo in debugging_memory_issues.md

2 docs/memory/debugging_memory_issues.md

2

docs/memory/debugging_memory_issues.md