From: Mario Hewardt Date: Thu, 9 May 2019 18:46:13 +0000 (-0700) Subject: Update intermittent_memory_spike.md X-Git-Tag: submit/tizen/20190813.035844~6^2^2~33^2~5 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=ea047f67da8f2585f37d70735d218a1f6602b813;p=platform%2Fcore%2Fdotnet%2Fdiagnostics.git Update intermittent_memory_spike.md --- diff --git a/documentation/tutorial/intermittent_memory_spike.md b/documentation/tutorial/intermittent_memory_spike.md index 392048c7e..87a2a7c6b 100644 --- a/documentation/tutorial/intermittent_memory_spike.md +++ b/documentation/tutorial/intermittent_memory_spike.md @@ -169,7 +169,7 @@ After 10-15 seconds, you will notice that triggerdump outputs the following foll That's it for creating your own diagnostics tool to support custom scenarios. ### Analyzing the core dump -Since the core dump that our tool generates is a standard core dump, we can use the same techniques illustrated in this tutorial to analyze why we're seeing intermitten high memory conditions. +Since the core dump that our tool generates is a standard core dump, we can use the same techniques illustrated in [Scenario - App is leaking memory](app_is_leaking_memory_eventual_crash.md) to analyze why we're seeing intermitten high memory conditions.