Blazor WASM Error on iOS Safari - RangeError: Out of Memory

[kyletinsley]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When loading Blazor WASM apps in iOS Safari, the following error is encountered, causing all apps to fail to load:
RangeError: Out of memory

I've encountered this error in every app I've written. To ensure the issue was not within my code, I created a new project using the standard WASM template in VS (counter/weather) and made no modifications.

I then deployed the default/unmodified app to Azure and repeated my testing. The error is encountered randomly when refreshing Safari on iOS (about every 5th refresh). I've experienced this on multiple iPhones and verified on BrowserStack using several iOS devices and Safari versions.

Here's the deployed base app:
https://blazor7-test.azurewebsites.net

This is s screenshot I took from BrowserStack:

Expected Behavior

App should load successfully, as it does in other browsers.

Steps To Reproduce

1. Using the standard .NET7 Blazor WebAssembly project template, create a new project.
2. Deploy that app to Azure app services.

Exceptions (if any)

RangeError: Out of Memory

.NET Version

7.0.100

Anything else?

No response

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

When loading Blazor WASM apps in iOS Safari, the following error is encountered, causing all apps to fail to load:
RangeError: Out of memory

I've encountered this error in every app I've written. To ensure the issue was not within my code, I created a new project using the standard WASM template in VS (counter/weather) and made no modifications.

I then deployed the default/unmodified app to Azure and repeated my testing. The error is encountered randomly when refreshing Safari on iOS (about every 5th refresh). I've experienced this on multiple iPhones and verified on BrowserStack using several iOS devices and Safari versions.

Here's the deployed base app:
https://blazor7-test.azurewebsites.net

This is s screenshot I took from BrowserStack:

Expected Behavior

App should load successfully, as it does in other browsers.

Steps To Reproduce

1. Using the standard .NET7 Blazor WebAssembly project template, create a new project.
2. Deploy that app to Azure app services.

Exceptions (if any)

RangeError: Out of Memory

.NET Version

7.0.100

Anything else?

No response

Author:	kyletinsley
Assignees:	-
Labels:	arch-wasm, untriaged, area-VM-meta-mono
Milestone:	-

[pavelsavara]

I see var INITIAL_MEMORY=Module["INITIAL_MEMORY"]||536870912 in the dotnet.js, this is probably duplicate of #61925

[pavelsavara]

@kyletinsley
What does your dotnet workload list print ?

[kyletinsley]

[pavelsavara]

@kyletinsley
could you please build/publish your project with -bl and share with me the binlog ?
Also please check what value INITIAL_MEMORY has, search inside your dotnet*.js

I'm trying to understand what triggers the re-link for you.
I could not reproduce it on vanilla blazor template.
Are you passing some MSBuild switches on commandline ? Or adding them to the .csproj in your real project ?

Update: I figured it out, thanks!

[pavelsavara]

Now I understand, just the installation of the wasm-tools workload always triggers re-link and you get.

Compiling native assets with emcc with -Oz. This may take a while ...
...
Linking for initial memory $(EmccInitialHeapSize)=536870912 bytes

[pavelsavara]

Now I understand, just the installation of the wasm-tools workload always triggers re-link and you get.

@radical @lewing
I think we should not change behavior of the build just by installing the workload.
I would rather have people also opt in via some msbuild property.
What do you think ?

[pavelsavara]

Fixed by #80849