Summary
After importing a vault successfully into PearPass Desktop, I connected the PearPass browser extension in Chromium. Shortly after the
extension connected, the desktop app appeared to crash or freeze. Logs show a very large burst of FETCH_FAVICON requests and many
Favicon not found errors, but no clean crash stack or Crashpad dump.
Environment
- PearPass Desktop: 2.1.0
- OS: Linux
- Browser: Chromium
- Browser extension: PearPass extension
- Install/runtime appears to be Nix-packaged
Steps to Reproduce
- Import an existing vault into PearPass Desktop using a vault invite/link.
- Open PearPass Desktop and unlock the vault.
- Connect the PearPass browser extension from Chromium.
- Wait for the extension/desktop sync to start.
Expected Result
PearPass Desktop should stay responsive and the browser extension should connect normally.
Actual Result
PearPass Desktop becomes unresponsive or appears to crash shortly after the Chromium extension connects.
Relevant Log Observations
The extension/native messaging path appears to connect successfully:
2026-05-31T08:27:09.760Z Received command: ENCRYPTION_GET { key: 'nm.client.data' }
2026-05-31T08:27:09.764Z Received command: ENCRYPTION_GET { key: 'nm.identity.pairingSecret' }
2026-05-31T08:27:09.766Z Received command: ENCRYPTION_GET { key: 'nm.identity.ed25519' }
2026-05-31T08:27:09.767Z Received command: ENCRYPTION_GET { key: 'nm.identity.x25519' }
Immediately before/around this, the app floods the logs with favicon requests:
Sending request: FETCH_FAVICON
Received command: FETCH_FAVICON { url: '[REDACTED]' }
Error fetching favicon: Error: Favicon not found
I counted roughly 3,951 favicon-related log lines around the reproduction window.
No obvious crash stack was logged:
- No worklet exit
- No uncaught exception
- No Crashpad dump found except Crashpad/client_id
### Notes
This may be related to the desktop app fetching favicons for many imported vault records at once after extension sync/unlock. It
would help if favicon fetching were throttled, deduplicated, skipped for invalid/internal URLs, or made non-blocking so it cannot
freeze the desktop app.
Summary
After importing a vault successfully into PearPass Desktop, I connected the PearPass browser extension in Chromium. Shortly after the
extension connected, the desktop app appeared to crash or freeze. Logs show a very large burst of
FETCH_FAVICONrequests and manyFavicon not founderrors, but no clean crash stack or Crashpad dump.Environment
Steps to Reproduce
Expected Result
PearPass Desktop should stay responsive and the browser extension should connect normally.
Actual Result
PearPass Desktop becomes unresponsive or appears to crash shortly after the Chromium extension connects.
Relevant Log Observations
The extension/native messaging path appears to connect successfully: