Codex extension crashes the page

[splitice]

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Chrome
• Local OS: Windows 11
• Remote OS: Debian Trixie
• Remote Architecture: x64
• code-server --version: 4.116.0

Steps to Reproduce

Spend a day closing issues with codex.

Expected

No issue

Actual

Relyably within 4-5 hours you will start getting

I am currently poisiting that something is being stored into indexdb or something client side (ideas?) thats causing a crash.

Seems to be getting worse too.

Logs

Nothing of interest on the server side.

Screenshot/Video

No response

Does this bug reproduce in native VS Code?

No, this works as expected in native VS Code

Does this bug reproduce in VS Code web?

I did not test VS Code web

Does this bug reproduce in GitHub Codespaces?

I did not test GitHub Codespaces

Are you accessing code-server over a secure context?

• I am using a secure context.

Notes

I have tested removing nearly every other extension, it appears to be code-server + codex.

Happy to get logs if you can provide some indication on how to, there doesnt appear to be anything on the server side as this seems to trigger a client side bug.

[linear-code]

DEVEX-483

[splitice]

I have held of for a while on posting this issue under the hopes I could get something captured but there doensnt seem to be any chrome logs for breakpoint errors that I can find.

And I eliminated all extensions other than Codex.

Memory usage of the server component seems fine and the server component remains running after clients restart. Although any codex running tasks have stopped.

Frequency seems to be increasing which is why I am currently leaning towards something like indexdb / local storage. I am guessing this is also a difference between electron and chrome likely.

[code-asher]

code-server just wraps VS Code web so I would recommend testing it directly to see if it reproduces (code serve-web). If it does, that would let us report it upstream where they probably know a lot more about what might be going wrong.

If it does not reproduce, that would suggest it could be our patches but I am not sure how any of our patches could cause this.

One other idea to try is the latest version to see if anything has changed.

I have seen some reports of memory leaks on the client side, maybe this is related. Possibly recording the memory usage in Chrome will help debug.

[splitice]

Length of client session does not seem like a variable as I had one today after 10 minutes of a fresh system reboot. So its client side crash, but server side runtime? Or potentially totally unrelated to to time.

[code-asher]

Interesting, so it could be caused by some specific action performed during those 10 minutes rather than a gradual memory leak. I think probably profiling will be needed to debug it. If you know the specific steps you did I could try them as well.

[splitice]

Do you have any suggestions for getting something of interest in log form?

I have a *.dmp file from todays crash. I also tested keeping a chrome tab open and verified that when it crashes its the PWA process (all windows) that crash, the chrome tab was unaffected.

Potentially something about having multiple PWA windows open doing things?

[code-asher]

Do you have any suggestions for getting something of interest in log form?

I am not sure the logs will turn up anything useful, but perhaps running code-server with --log verbose will turn up something interesting, either in the browser console or in the extension host logs.

Potentially something about having multiple PWA windows open doing things

It only crashes if you have multiple PWA windows open? Or it just crashes faster? Nothing off the top of my head comes to mind that would cause an issue if multiple windows are opened (and they should each have their own extension host process) but I really only have surface-level understanding of VS Code.

[code-asher]

Hmm or actually maybe like you said it is a crash related to IndexedDB, if they both try to write at the same time? Are you able to capture any of the browser-side logs in the dev console? I am not sure if this would cause a full crash though, or if it would "just" cause database corruption.

[splitice]

Any idea how to get brower side logs or dev tools in PWA mode?

I ran it in 6 tabs for all of yesterday without any crashes. I'll repeat today.

If I get another day or two without crashes I am willing to say its only in PWA mode.

[splitice]

I think I can confirm the issue only occurs in PWA mode.

[code-asher]

Huh that is really interesting, I am not sure what could be so different about the PWA, in theory it should be pretty much the same as a tab.

What worked for me to open the dev tools was to press F12 (but not in an editor or terminal because it will consume the key, so you have to click on the titlebar or sidebar or somewhere else then press F12).

I will leave two PWA windows open and see if it reproduces for me.