Occasionally, vscodium takes 1 minute+ to open from a cold start

[REALERvolker1]

Describe the bug
Windows take a VERY long time to open, from invoking the codium command, to seeing a window

Please confirm that this problem is VSCodium-specific

• This bug doesn't happen if I use Microsoft's Visual Studio Code. It only happens in VSCodium.

This happens occasionally, and the few times I have tested, it has not happened with Visual Studio Code, but due to the nature of this bug, it would not be a good idea to rule this out.

Please confirm that the issue/resolution isn't already documented

• I checked the Docs page and the Troubleshooting page and my issue is not mentioned there.

To Reproduce
Steps to reproduce the behavior:

1. Run the command codium in a terminal window
2. wait a couple minutes for the window to open

Expected behavior
I expected the application to either always open promptly, or always open 1+ minutes after running the command. At least some consistency.

Screenshots
I'll do you one better, here is the main.log I obtained by running with the CLI flag --log debug. I closed the window shortly after it opened, which probably explains the last couple messages.

2025-12-20 14:03:54.514 [debug] Starting VSCodium
2025-12-20 14:03:54.514 [debug] from: /usr/lib/vscodium
2025-12-20 14:03:54.514 [debug] args: {"_":[],"diff":false,"merge":false,"add":false,"remove":false,"goto":false,"new-window":false,"reuse-window":false,"wait":false,"help":false,"list-extensions":false,"show-versions":false,"pre-release":false,"update-extensions":false,"version":false,"verbose":false,"log":["debug"],"status":false,"prof-startup":false,"no-cached-data":false,"prof-v8-extensions":false,"disable-extensions":false,"disable-lcd-text":false,"disable-gpu":false,"disable-chromium-sandbox":false,"sandbox":false,"telemetry":false,"debugRenderer":false,"enable-smoke-test-driver":false,"logExtensionHostCommunication":false,"skip-release-notes":false,"skip-welcome":false,"disable-telemetry":false,"disable-updates":false,"use-inmemory-secretstorage":false,"disable-workspace-trust":false,"disable-crash-reporter":false,"skip-add-to-recently-opened":false,"open-url":false,"file-write":false,"file-chmod":false,"force":false,"do-not-sync":false,"do-not-include-pack-dependencies":false,"trace":false,"trace-memory-infra":false,"preserve-env":false,"force-user-env":false,"force-disable-user-env":false,"open-devtools":false,"disable-gpu-sandbox":false,"__enable-file-policy":false,"enable-coi":false,"enable-rdp-display-tracking":false,"disable-layout-restore":false,"no-proxy-server":false,"no-sandbox":false,"nolazy":false,"force-renderer-accessibility":false,"ignore-certificate-errors":false,"allow-insecure-localhost":false,"disable-dev-shm-usage":false,"profile-temp":false,"logsPath":"/home/vlk/.config/VSCodium/logs/20251220T140354"}
2025-12-20 14:03:54.557 [info] update#setState disabled
2025-12-20 14:03:54.557 [info] update#ctor - updates are disabled as there is no update URL
2025-12-20 14:04:46.695 [debug] Terminal profile not validated pwsh ["pwsh"]
2025-12-20 14:04:47.161 [debug] ProxyResolver#loadSystemCertificates count 145
2025-12-20 14:04:47.161 [debug] ProxyResolver#loadSystemCertificates parse error Error: error:0900006e:PEM routines:OPENSSL_internal:NO_START_LINE
    at new X509Certificate (node:internal/crypto/x509:119:21)
    at /usr/lib/vscodium/node_modules/@vscode/proxy-agent/out/index.js:742:48
    at Array.filter (<anonymous>)
    at Module.<anonymous> (/usr/lib/vscodium/node_modules/@vscode/proxy-agent/out/index.js:740:26)
    at Generator.next (<anonymous>)
    at fulfilled (/usr/lib/vscodium/node_modules/@vscode/proxy-agent/out/index.js:32:58)
2025-12-20 14:04:47.165 [debug] ProxyResolver#loadSystemCertificates count filtered 144
2025-12-20 14:05:03.413 [info] Extension host with pid 10827 exited with code: 0, signal: unknown.
2025-12-20 14:05:03.439 [error] [UtilityProcess id: 1, type: fileWatcher, pid: 10817]: crashed with code 15 and reason 'killed'

Desktop (please complete the following information):

• OS: Arch Linux
• Architecture x86_64
• Version yes
• App Manager Chaotic-AUR vscodium-electron
• Sandboxed no

Additional context
Is this seriously waiting a whole minute just because I don't have powershell pwsh installed on my system???

Forgot to add this other context: Sometimes when I have an external monitor connected to my laptop, it always opens near-instantly. Also, when I already have one window open, opening another window happens near-instantly as well.

[daiyam]

Additional context Is this seriously waiting a whole minute just because I don't have powershell pwsh installed on my system???

I was wondering why pwsh on a Arch linux...
Can you try vscodium or vscodium-bin?
What are your settings? In particular terminal.integrated.defaultProfile.linux?

[REALERvolker1]

I have terminal.integrated.defaultProfile.linux set to null

The rest of my settings are here

I still have some other testing to do with the vscodium package.

[daiyam]

I have:

[main 2025-12-23T23:50:56.399Z] Terminal profile not validated zsh [ 'zsh' ]
[main 2025-12-23T23:50:56.399Z] Terminal profile not validated fish [ 'fish' ]
[main 2025-12-23T23:50:56.399Z] Terminal profile not validated tmux [ 'tmux' ]
[main 2025-12-23T23:50:56.400Z] Terminal profile not validated pwsh [ 'pwsh' ]

So the pwsh doesn't seem to be the issue.

Can you try to disable the rust extensions (they can be quite heavy)?
Also, can you try the command codium --verbose?