11## Memory leaks
22
3- Riot usually emits slow behaviour just before it is about to crash. Getting a
3+ Element usually emits slow behaviour just before it is about to crash. Getting a
44memory snapshot (below) just before that happens is ideal in figuring out what
55is going wrong.
66
@@ -14,14 +14,14 @@ this happens though so we can try and narrow down what might have gone wrong.
1414## Memory profiles/snapshots
1515
1616When investigating memory leaks/problems it's usually important to compare snapshots
17- from different points in the Riot session lifecycle. Most importantly, a snapshot
17+ from different points in the Element session lifecycle. Most importantly, a snapshot
1818to establish the baseline or "normal" memory usage is useful. Taking a snapshot
19- roughly 30-60 minutes after starting Riot is a good time to establish "normal"
19+ roughly 30-60 minutes after starting Element is a good time to establish "normal"
2020memory usage for the app - anything after that is at risk of hiding the memory leak
2121and anything newer is still in the warmup stages of the app.
2222
2323** Memory profiles can contain sensitive information.** If you are submitting a memory
24- profile to us for debugging purposes, please pick the appropriate Riot developer and
24+ profile to us for debugging purposes, please pick the appropriate Element developer and
2525send them over an encrypted private message. * Do not share your memory profile in
2626public channels or with people you do not trust.*
2727
@@ -42,7 +42,7 @@ While the profile is in progress, the tab might be frozen or unresponsive.
4242
43431 . Press CTRL+SHIFT+I (I as in eye).
44442 . Click the Memory tab.
45- 3 . Select "Heap Snapshot" and the riot.im VM instance (not the indexeddb one).
45+ 3 . Select "Heap Snapshot" and the app.element.io VM instance (not the indexeddb one).
46464 . Click "Take Snapshot".
47475 . Wait a bit (coffee is a good option).
48486 . When the save button appears on the left side of the panel, click it to save the
0 commit comments