Bug 1821107 Comment 14 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

This shows up **a lot** on ChatGPT. Especially when you have a very long chat and send a message to ChatGPT (bug 1963578).

Here are the most interesting stats (first column is counts) after opening a large chat and sending a message (most of the `get` calls happened while I was waiting for the reply):
```
975      JS WeakMap constructor
...
14033    WeakMap get, miss, 1 entries
73299    WeakMap get, hit: 2 entries
6758088  WeakMap get, hit: 386 entries
19908292 WeakMap get, hit: 388 entries
26577476 WeakMap get, hit: 1 entries
```
They seem to use nested `WeakMap`s. I *think* the outer one has 386-388 entries in this case, but this number goes up with the length of the conversation.

If ChatGPT's response is longer, the number of `WeakMap.prototype.get` calls becomes much much higher even. The next step is figuring out what they're doing exactly to trigger this.
This shows up **a lot** on ChatGPT. Especially when you have a very long chat and send a message to ChatGPT (bug 1963578).

Here are the most interesting stats (first column is counts) after opening a large chat and sending a message (most of the `get` calls happened while I was waiting for the reply):
```
975      JS WeakMap constructor
...
14033    WeakMap get, miss: 1 entries
73299    WeakMap get, hit: 2 entries
6758088  WeakMap get, hit: 386 entries
19908292 WeakMap get, hit: 388 entries
26577476 WeakMap get, hit: 1 entries
```
They seem to use nested `WeakMap`s. I *think* the outer one has 386-388 entries in this case, but this number goes up with the length of the conversation.

If ChatGPT's response is longer, the number of `WeakMap.prototype.get` calls becomes much much higher even. The next step is figuring out what they're doing exactly to trigger this.

Back to Bug 1821107 Comment 14