Safari 18.4 (macOS 15.4) Crash Occurs During Bitwarden Safari Extension Activity

[uptimejeff]

Steps To Reproduce

1. Enable Bitwarden Safari extension.
2. Unlock the vault or save a new login.
3. Wait approximately 30–120 seconds.
4. Safari crashes unexpectedly.

Expected Result

Safari should continue functioning normally without crashing after interacting with the Bitwarden extension.

Actual Result

Safari crashes unexpectedly within 30–120 seconds after interacting with the Bitwarden extension.

Screenshots or Videos

No screenshots or videos.

Additional Context

• All other Safari extensions are disabled (only Bitwarden active).
• Local storage for the Bitwarden extension has been cleared.
• Crashes observed only when Bitwarden extension is active; further testing with it fully disabled is pending.
• Crash .ips logs show crashes occur during WebPageProxy::makeFirstResponder.
• System logs show frequent teardown/restart cycles of com.bitwarden.desktop.safari before crash.
• No unusual CPU or memory load was present at time of crash.
• The crash has been observed reproducibly across multiple days and sessions.

Thank you for your work on Bitwarden.
Happy to assist with additional diagnostics or testing if needed.

Operating System

macOS

Operating System Version

macOS 15.4 (24E248)

Web Browser

Safari

Browser Version

Safari 18.4 (20621.1.15.11.10)

Environment Versions

Version 2025.3.0 (39877)

Safari-2025-04-26-181100.ips.txt
crash_watch.log
logs_2025-04-25_13-20-20.txt
logs_2025-04-26_15-41-25.txt
logs_2025-04-26_18-10-02.txt
logs_2025-04-26_18-12-31.txt
Safari-2025-04-25-132015.ips.txt
Safari-2025-04-26-154119.ips.txt
Safari-2025-04-26-180957.ips.txt

Issue Tracking Info

• I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.

[bitwarden-bot]

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-20651

[rmcdowell-bitwarden]

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

[uptimejeff]

Quick status update:

• At the time of the original report, Bitwarden was the only active Safari extension (all others were disabled).
• I disabled the Bitwarden Safari extension approximately 27 hours ago.
• Since disabling Bitwarden, Safari has remained stable — no crashes detected during this time.
• No other extensions are active currently.

I plan to continue monitoring for at least another 24 hours to be thorough.

Please let me know if there’s any other information I can provide or testing I can assist with.

[uptimejeff]

Additional context and clarification:

• In the original report, I stated that a crash might occur within 30–120 seconds after interacting with the Bitwarden extension.
• However, after further observation, the crash is not immediate — it tends to occur sporadically throughout the workday (typically 3–5 crashes over ~8–10 hours of normal use).
• It may take several hours before the first crash occurs.

Additional environment detail:

• I actively use Safari Profiles, typically with 2–3 profile windows open simultaneously.
• The Bitwarden extension is enabled and used across all Safari profiles.
• Crash incidents have occurred regardless of which profile window was in active use.

Add'l testing:
I re-enabled the bitwarden extension for my primary profile only.
I'll run for 24-48hours and will track any crashes and report back details and logs.

[uptimejeff]

Update:

After re-enabling the Bitwarden Safari extension, Safari crashes resumed after several hours of normal use.
No other Safari extensions were active during this time.

Crashes consistently occur after interacting with the webauthn-fallback-connector.html page.
Before the crash, the Bitwarden WebAuthn UI (e.g., "Read security key" button and checkbox) becomes unresponsive to clicks — requiring double-clicks or fails to register interaction entirely.

From Safari’s Web Inspector console, I observed:
Source Map “https://vault.bitwarden.com/styles.ec046a0df147569f2a1a.css.map” has invalid “sourcesContent” NotAllowedError: The document is not focused.

Crash logs and system logs captured immediately after the incidents are attached.

Additional notes:

• This behavior has only been observed on my current Mac and macOS user profile.
• I have not yet tested in a new user account or on a separate device.
• If helpful, I can reset my Safari environment, test under a clean profile, or assist with focused reproduction scenarios.

crash_watch.log
logs_2025-04-29_16-30-31.txt
Safari-2025-04-29-163028.ips.txt
logs_2025-04-29_16-01-11.txt
Safari-2025-04-29-160109.ips.txt
logs_2025-04-29_15-42-03.txt
Safari-2025-04-29-154153.ips.txt

[uptimejeff]

Update:

Over the last 4 days, Safari has remained completely stable with the Bitwarden extension disabled across all Safari profiles.

Today, I re-enabled the Bitwarden extension for my primary Safari profile.

When attempting to log in via the extension:

• I enter the email address and click “Use single sign-on” (SSO).
• Safari crashes immediately after clicking — this occurs 100% of the time and across all Safari profiles.
• Note: Our organization does not have SSO enabled.

In Safari’s developer console, I observed the following warning prior to the crash:
[Warning] Source Map “safari-web-extension://11C69509-D2CA-421C-950D-15DDDA63D963/popup/main.css.map” has invalid “sourcesContent”

Crash logs and supporting system logs are attached below for this sequence:
logs_2025-05-03_19-48-31.txt
crash_watch.log
logs_2025-05-03_19-57-19.txt
Safari-2025-05-03-195717.ips.txt
Safari-2025-05-03-194633.ips.txt
logs_2025-05-03_19-46-15.txt
Safari-2025-05-03-194532.ips.txt
logs_2025-05-03_19-44-00.txt
Safari-2025-05-03-194352.ips.txt

Please let me know if you'd like me to test anything else or provide additional diagnostic info.

[uptimejeff]

Additional update:

I’ve tested on a second Mac (same versions of macOS and Safari), and the issue does not occur — Bitwarden functions normally there.

On my original machine, the crash is still 100% reproducible when interacting with the Bitwarden extension's WebAuthn flow (clicking "Use single sign-on"). This happens even with all other extensions disabled, across all Safari profiles.

This suggests the issue may be specific to my local Safari environment or extension data.

To confirm this, I plan to fully reset Safari and test again.
If the issue resolves, that would point to a corruption or configuration problem unique to this instance of Safari.

Please let me know if you'd like any additional diagnostics before I perform the reset. I'm happy to assist further.

[trmartin4]

@uptimejeff thank you for the update. I do not think we need any additional information at this time, but we would be curious to hear if this resolves with a reset of Safari.

[uptimejeff]

To narrow down, here's what I did

Within my MacOS user:

• Cleared website data from Safari preferences
  tested, safari crashes interacting with webauthn
• Used AppCleaner to locate safari-related files/caches/containers and removed them (screenshot)
  tested, safari crashes interacting with webauthn

Created a new MacOS user (same computer), Safari and BW extension had no issues from the new user.

Logged out of new-user test and logged in with my primary MacOS user.

• Used AppCleaner to identify and remove files/caches/containers for the Bitwarden.app (MAS)
  tested, safari crashes interacting with webauthn
• Disabled iCloud Sync for Safari
  tested, safari crashes interacting with webauthn
• Deleted BitWarden.app, reinstalled from MAS
  tested, safari crashes interacting with webauthn

Bitwarden.app authenticates with webauthn.

I have a 9MB 'log show' that covers the time period during steps above, I'll upload if relevant.
Attached screenshot shows the files identified and removed.
My next step will be to use fs_usage to identify all files access by the BW extension.

bitwarden-uninstall.pdf