diff options
author | Henrik Nord <[email protected]> | 2018-10-30 10:50:30 +0100 |
---|---|---|
committer | GitHub <[email protected]> | 2018-10-30 10:50:30 +0100 |
commit | 3094642858ec071f9e98cfa666b82e06648b5266 (patch) | |
tree | 13cb10ffcd1f86c3eac56f61724c269cb01d2c11 | |
parent | 02471973ddfcf28529295787f546df3e41c7c84a (diff) | |
parent | ac22658306841bf4dbed1d7cd3204438d23249a7 (diff) | |
download | otp-3094642858ec071f9e98cfa666b82e06648b5266.tar.gz otp-3094642858ec071f9e98cfa666b82e06648b5266.tar.bz2 otp-3094642858ec071f9e98cfa666b82e06648b5266.zip |
Merge pull request #2007 from isadd/patch-1
Update profiling.xml
-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> |