Boundary desktop v2.2.0 exhausted /dev/shm when doing OIDC login

[age9990]

Describe the bug
When ussing Boundary desktop v2.2.0, if doing OIDC login, and stops in "Authentication Pending", we can see /dev/shm usage keeps growing until full, and the Boundary desktop crashes. The issue is not present in v2.1.0 or earlier version of Boundary desktop.

To Reproduce
Steps to reproduce the behavior:

1. Run Boundary desktop v2.2.0
2. Do OIDC login, and stop s in "Authentication Pending"
3. Boundary desktop crashes when /dev/shm is exhausted.

Expected behavior
/dev/shm is not exhausted like in v2.1.0 or earlier version

Additional context
Add any other context about the problem here.

[ZedLi]

Hi @age9990!

Thanks for this bug report! I'd like to first collect some more info, do you mind adding:

• Environment you're running in (OS + version, CPU arch)
• Boundary controller version
• Desktop client logs

[age9990]

@ZedLi Thanks for quick reply.
Environment: Ubuntu 22.04, amd64
Boundary controller version: 0.17.2, 0.18.1
Desktop client logs: Only these logs, when the issue occurred, no log is printed.
| Version: Boundary v0.18.0
| Version Sha: 2e3fdb718cb5ed20017b124deb6f438310b9dd0f
|
| ==> cache started! Log data will stream in below:
[2024-12-13T02:07:10.766-00:00] [warn] Client Agent Status: {"error":"'boundary client-agent' is not supported on this platform."}
[2024-12-13T02:07:12.023-00:00] [warn] Client Agent Status: {"error":"'boundary client-agent' is not supported on this platform."}

[ZedLi]

Hello @age9990,

We haven't been able to reproduce this issue, do you happen to have any more info such as before and after results of your /dev/shm usage growing?

When you are using the OIDC login, does it end up opening the browser window for authentication or does it crash before it even gets to that?

[age9990]

Hi, @ZedLi , here is the procedure to reproduce the issue.

1. "boundary dev" to create a boundary server
2. Open Boundary desktop v2.2.0, Boundary controller url is "http://127.0.0.1:9200"
3. In "Sign In" page, select "Generated global scope initial oidc auth method"
4. Click "Sign In" button
5. The boundary desktop will stop in the page showing "Authentication Pending", and Google Chrome is automaticall started with a page "http://127.0.0.1:39281/authorize...", which is an interal oidc provider login page
6. No need to login, just stops at step 5
7. Use terminal to execute "watch df -h /dev/shm", we can see the usage of /dev/shm is continuously rising.

[ZedLi]

Thank you for the detailed reproduction steps! We're currently investigating this and will let you know what we find