Search Issue Tracker
Duplicate
Votes
5
Found in
2021.3.34f1
2022.3.19f1
2023.3.0b7
6000.0.0b11
Issue ID
UUM-63456
Regression
No
WebGL build fails when multithreading is turned on
Reproduction steps:
1. Open the user's attached project ("My Project 001") on the WebGL platform
2. Make sure that "Project Settings -> Player -> Publishing Settings -> Enable Native C/C++ Multithreading" is checked (For Unity 2021 and 2022, check notes)
3. Build the project
Expected result: The project gets built
Actual result: The Build fails after some time with an error message (Check notes)
Reproducible with: 2021.3.34f1, 2022.3.19f1, 2023.3.0b7
Reproducible on: macOS 14.2.1 (Intel), Windows 11 (User)
Not reproducible on: No other environment tested
Notes:
1. For Unity 2021 and 2022, a script needs to be used to enable multithreading. Download the attached "Editor" archive and extract it in the Assets folder. The script's directory should be "Assets/Editor/Threads.cs"
2. The error message:
{quote}
Internal build system error. BuildProgram exited with code 1.
System.ArgumentException: Another action is already registered for fdgdfgdfg/Build/d41d8cd98f00b204e9800998ecf8427e.js.unityweb
{quote}
3. The user reports that the Editor might sometimes crash during building. I was not able to reproduce any crashes and none are present in the logs provided by the user
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on RenderBufferManager::Textures::GetTempBuffer when rendering a specific scene
- The Inspector header is incorrectly displayed when scripts are recompiled while a Scriptable Object instance is selected
- NullReferenceException is thrown when overriding the UxmlObjectReferences in template instances
- Shaders created with Shader Graph generate a large amount of shader variants and cause slow build times when using a baked lightmap in BIRP
- Shader Graph Matrix property produces random output values when SRP Batcher is enabled
Resolution Note:
It would appear the underlying issue is the same as in UUM-35863 "NameFilesAsHashes feature has regressed". For Unity 2023.2, this issue was fixed in 2023.2.15f1, and by upgrading to it, I'm able to build the project without errors.
However, we found out that if you upgrade the project to 2023.3.0b11 or newer, which has the same fix for 2023.3, you will most likely start encountering a different error. It seems that the culprit of this issue is the Undertone plugin's WASM binaries, which seem to be incompatible with the new Wasm2023 feature set, which was introduced in 2023.3.0a16 — beginning from this version, the multithreading feature is coupled with the new Wasm2023 feature set. To resolve this issue, we advise you to see if there's a newer Wasm2023-compatible version of the plugin available, and if not, please contact the developer of the plugin, if they could provide such. We will gladly work with the developer of the plugin if they encounter issues with the matter.
Duplicate of another internal issue: UUM-35863: NameFilesAsHashes feature has regressed