Sessions take a very long time to open

[vmvartiainen]

Bug Description

Hive loads sessions extremely slowly before they can be opened.

Steps to Reproduce

1. Open Hive.
2. Navigate to the sessions view.
3. Try to open an existing session.
4. Observe the unusually long loading time before the session opens.

Expected Behavior

Sessions should open promptly without a long loading delay.

Actual Behavior

Sessions take a very long time to load before they become accessible.

Screenshots

Not provided.

Environment

• OS: macOS 26.3.1
• Hive Version: 1.0.81
• Node Version: 25.8.2
• Installation Method: Brew

Worktree/Project Details

• Git Version: 2.53.0
• Number of Worktrees: Unknown / not provided
• Repository Size: Unknown / not provided

AI Session Details

• AI Provider: OpenCode
• Session Type: Unknown / not provided
• Tools Used: terminal commands

Error Messages

No explicit error message was shown. The issue manifests as very slow session loading.

AI-generated issue report based on a user-provided bug description.

[morapelker]

is that only from the recent versions? or was always the case

[vmvartiainen]

is that only from the recent versions? or was always the case

I noticed it today after I updated to the newest version.

[morapelker]

does it happen for both empty/very low message count sessions and big long sessions? does it happen when you enter the session the first time? every time?

[vmvartiainen]

does it happen for both empty/very low message count sessions and big long sessions? does it happen when you enter the session the first time? every time?

1. does it happen for both empty/very low message count sessions and big long sessions -> yes but there is difference (correlation with session size)
2. does it happen when you enter the session the first time? -> yes but it's not that long, it's acceptable
3. every time? -> yes every time

[morapelker]

its not replicating on my end, for some reason it just works. Can you pin point the issue on your end? Or give me a minimal reproducible example?

[vmvartiainen]

Does this help?

When you open sessions, some processes continue to consume resources, and even after the session opens, CPU usage doesn’t decrease—it stays at a high level. It’s as if opening a session somehow leaves a process “running” and consuming CPU resources.

[morapelker]

so it takes a long time to load, but if you close the app and reopen it - does the same session still take a long time to load? since if its orphaned processes consuming cpu, restarting the app should close those processes and perform well again

[vmvartiainen]

so it takes a long time to load, but if you close the app and reopen it - does the same session still take a long time to load? since if its orphaned processes consuming cpu, restarting the app should close those processes and perform well again

If I close the program and reopen it, CPU usage is normal, but if I open sessions again, CPU usage starts to rise and stays high.

[BeeRupiko]

https://www.electronjs.org/docs/latest/tutorial/performance
Profiling the app could help.

[morapelker]

im going to deploy a new version with a potential fix #217
let me know, after updating, if its better/worse/same

[vmvartiainen]

Tested version 1.0.84 -> I'd say it's even worse now.

[morapelker]

So what I would suggest is, since I cannot actually see this on my end. Can you try and identify the version which caused the issue? Maybe even the specific commit, using git bisect? This would point us in the right direction to the problematic commit, so I can check what was changed there and fix the problem. This would simply be you doing a git bisect, running the app id say 4-5 times until you find the correct commit.

[morapelker]

you have access to codex as well right? does it happen using codex as well?

[vmvartiainen]

I've access. I'll be back once I've finished the tests. I've been a little busy lately.