Skip to content

Commit 0f159c5

Browse files
committed
Update memory-profiles-and-leaks.md
1 parent f2b9bd4 commit 0f159c5

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

docs/memory-profiles-and-leaks.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
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
44
memory snapshot (below) just before that happens is ideal in figuring out what
55
is 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

1616
When 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
1818
to 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"
2020
memory usage for the app - anything after that is at risk of hiding the memory leak
2121
and 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
2525
send them over an encrypted private message. *Do not share your memory profile in
2626
public 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

4343
1. Press CTRL+SHIFT+I (I as in eye).
4444
2. 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).
4646
4. Click "Take Snapshot".
4747
5. Wait a bit (coffee is a good option).
4848
6. When the save button appears on the left side of the panel, click it to save the

0 commit comments

Comments
 (0)