[v2] Webview crashes on macOS 26 (Tahoe)

[vegidio]

Description

I have a Wails application that makes many UI updates in a short period of time and this has always worked fine, but recently the webview started to crash and the app screen goes blank, however the Go code continues to work fine in the background. This doesn't happen if I open my application frontend using the browser (Firefox); the screen never goes blank.

Nothing major happened in my in app recently; the only difference in my environment was the installation of the newest macOS 26, so I suspect that maybe macOS changed something on how webviews work?

To Reproduce

1. Create an app that receives many UI updates in a short period of time (a few changes per second)
2. The webview in crash after some seconds
3. Open the same application on the browser and the problem doesn't happen

Expected behaviour

The webview doesn't crash on macOS 26

Screenshots

No response

Attempted Fixes

No response

System Details

# Wails
Version | v2.10.2


# System
┌────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
| OS           | MacOS                                                                                                                       |
| Version      | 26.0                                                                                                                        |
| ID           | 25A354                                                                                                                      |
| Branding     |                                                                                                                             |
| Go Version   | go1.25.1                                                                                                                    |
| Platform     | darwin                                                                                                                      |
| Architecture | arm64                                                                                                                       |
| CPU 1        | Apple M2 Max                                                                                                                |
| CPU 2        | Apple M2 Max                                                                                                                |
| GPU          | Chipset Model: Apple M2 Max Type: GPU Bus: Built-In Total Number of Cores: 30 Vendor: Apple (0x106b) Metal Support: Metal 4 |
| Memory       | 64GB                                                                                                                        |
└────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

# Dependencies
┌────────────────────────────────────────────────────────────────────┐
| Dependency                | Package Name | Status    | Version     |
| Xcode command line tools  | N/A          | Installed | 2412        |
| Nodejs                    | N/A          | Installed | 22.19.0     |
| npm                       | N/A          | Installed | 10.9.3      |
| *Xcode                    | N/A          | Installed | 16.4 (16F6) |
| *upx                      | N/A          | Available |             |
| *nsis                     | N/A          | Available |             |
|                                                                    |
└───────────────────── * - Optional Dependency ──────────────────────┘

Additional context

No response

[github-actions]

👋 Thanks for reporting this issue! To help us investigate, could you please:

1. Add the output of wails doctor if not already included
2. Provide clear steps to reproduce the issue
3. If possible, create a minimal reproduction of the issue

This will help us resolve your issue much faster. Thank you!

[dosubot]

Hi @vegidio! I'm Dosu and I’m helping the wails team.

This is a known issue with Wails v2 on macOS 26—rapid UI updates can cause the embedded webview to crash and the app screen to go blank, while the Go backend keeps running. The problem is triggered by changes in macOS 26 that Wails v2 doesn't handle, leading to segmentation faults in the native code. There are currently no official fixes or workarounds for v2, and the issue does not occur in standalone browsers because it is specific to the embedded webview integration. Compatibility improvements for macOS 26 are being added in Wails v3, so testing your app with v3 is recommended if you need support for the latest macOS versions. More details are available in this related issue: #4388.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[vegidio]

@dosu It's great compatibility improvements are added for macOS 26, but given that v3 is still in alpha, I think it would make sense to make sure v2 works until v3 has a stable version.

[dosubot]

I completely understand your concern about maintaining v2 support while v3 is still in alpha. At the moment, all recent compatibility work for macOS 26 is focused on Wails v3, and there are no official fixes, backports, or community workarounds for the webview crash issue in v2 on macOS 26. The changelogs, issues, and merged pull requests confirm that v2 is not receiving updates for this OS version, and the crash is likely due to breaking changes in macOS 26's native APIs that v2 doesn't handle source.

If you need to run on macOS 26, the only path forward is to monitor v3's progress and test your app with v3 alpha. For production, v2 remains recommended, but only on supported OS versions source. If any new information or fixes for v2 become available, I'll share them here.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[leaanthony]

I can't reproduce. If you can provide a minimal reproducible example then we can take a look but so far, works as expected:

[vegidio]

I don't have a minimal reproducible example, but I can show the problem in my project.

The folder gui/ is a Wails 2 application, so you can recreate the problem by running the app on that folder:

1. Enter a Reddit URL with many images, like https://www.reddit.com/r/pics/
2. Click on the button "Query"
3. Select all images and click on "Download"

A new window will appear showing the download progress of each image. After some time running the webview disappears but the Go code continues to run in the background downloading the images. If I open the Wails frontend using an external browser the problem doesn't happen.

I create this app almost 1 years ago and never had this problem. I only noticed this after installing MacOS 26. I'm also attaching a video here for reference, showing the problem; I hope this helps:

webview.crash.mov

Thanks.

[vegidio]

@leaanthony I’ve confirmed that the reason for the WebView crashing on macOS 26 is the number of UI updates happening in a short period of time. I verified this in two ways:

1. I asked a friend who hadn’t yet upgraded to macOS 26 to run my application. It worked as expected. After he upgraded to macOS 26, the same app that had worked before started crashing.
2. I modified my frontend code (React.js) to reduce the frequency of UI updates, and the app began working again for me.

While reducing UI updates seems to “solve” the issue, this feels more like a workaround than a true solution, since everything worked fine before without any code changes.

To me, this points to an issue with WKWebView on macOS 26 rather than with Wails. It looks like Apple may have changed something to make frequent UI updates more restrictive. I’m not sure if Wails can do anything to work around this, but I wanted to document my findings here, since I’m now convinced that something changed in macOS 26.

[leaanthony]

So this can be triggered purely by JavaScript? That sounds bad!