diff options
| author | xbofang <[email protected]> | 2018-10-26 14:00:55 +0800 |
|---|---|---|
| committer | GitHub <[email protected]> | 2018-10-26 14:00:55 +0800 |
| commit | ac22658306841bf4dbed1d7cd3204438d23249a7 (patch) | |
| tree | 447cd80f81082566cfa4fe48bf8826c7e6126e2b | |
| parent | c37f7a2215646c85c1ae12303f07bc9bc27b75ae (diff) | |
| download | otp-ac22658306841bf4dbed1d7cd3204438d23249a7.tar.gz otp-ac22658306841bf4dbed1d7cd3204438d23249a7.tar.bz2 otp-ac22658306841bf4dbed1d7cd3204438d23249a7.zip | |
Update profiling.xml
memory typo
| -rw-r--r-- | system/doc/efficiency_guide/profiling.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/system/doc/efficiency_guide/profiling.xml b/system/doc/efficiency_guide/profiling.xml index cdc80289cf..5ec1f1be6e 100644 --- a/system/doc/efficiency_guide/profiling.xml +++ b/system/doc/efficiency_guide/profiling.xml @@ -94,7 +94,7 @@ <p>The above slogan is one of the more common reasons for Erlang to terminate. For unknown reasons the Erlang Run-Time System failed to allocate memory to use. When this happens a crash dump is generated that contains information - about the state of the system as it ran out of mmeory. Use the + about the state of the system as it ran out of memory. Use the <seealso marker="observer:cdv"><c>crashdump_viewer</c></seealso> to get a view of the memory is being used. Look for processes with large heaps or many messages, large ets tables, etc.</p> |