XPipe opens the vault very slowly

XPipe opens the vault very slowly

Summary

When opening the vault in XPipe, startup takes approximately 35 seconds after entering the Bitwarden master password.

This delay occurs even though the vault data can be retrieved quickly via the Bitwarden CLI.

Environment

• XPipe version: 24.3
• Password manager: Vaultwarden
  • Self-hosted and operated on-premises
  • Approximately 400 passwords/items
  • bw list items takes approximately 1 second
• Vault access: Role-based access control
  • 5 roles in total
  • 1 default role for all users
  • 4 user-specific roles
  • Users generally have access to only 2 roles
• GitLab: Self-hosted and operated locally
  • Vault size according to Git: 3.19 MiB
  • Repository contains 16,462 objects
  • Vault currently contains 161 connections
  • Vault currently contains 23 identities
  • Only a few identities are currently stored in the password manager

Actual behavior

After entering the Bitwarden master password, XPipe takes approximately 35 seconds to fully open the vault and make it usable.

Expected behavior

The vault should open within a few seconds.

Retrieving the approximately 400 items using the Bitwarden CLI command bw list items takes only around 1 second.

Steps to reproduce

1. Start XPipe 24.3.
2. Open the vault.
3. Enter the Bitwarden master password.
4. Measure the time until the vault is fully opened and usable.

Additional observations

The size of the Git repository and the number of connections and identities appear to be relatively small.

The startup time increases significantly with each additional role that is added. This suggests that the role-based access control configuration may have a direct impact on vault opening performance.

The significantly shorter execution time of bw list items suggests that the delay may not occur during the retrieval of the vault data itself, but rather during subsequent processing within XPipe.

Possible causes could include:

• Evaluation of role-based access permissions
• Processing each role sequentially
• Processing the Git history or the 16,462 repository objects
• Processing of connections and identities
• Repeated or sequential requests to Vaultwarden
• Decryption or synchronization of the vault data

Questions

• Are there any known performance issues when opening a vault with role-based access control enabled?
• Is the startup time expected to increase significantly with each additional role?
• Is there a way to log or measure the individual processing steps?
• Which debug logs or diagnostic data would be required for further analysis?