Search Issue Tracker
Active
Votes
0
Found in
1.2.1
Issue ID
UUM-136482
Regression
No
Adding profiling or missing submodule handling to multithreaded Emscripten 4 builds does not work.
What is happening?
1. Open "Submodule Test Project" with Unity 6.6
2. Build project with "Multithreading" enabled.
3. Open Window > Web Optimization > Submodule Stripping
4. Select the build
5. Click on "Add profiling"
6. Click on "Run".
The build is not instrumented and submodule profiling does not work.
What do we expect to happen?
The build is instrumented and submodule profiling works.
Additional Resources
The reason is that on multithreaded Emscripten 4 builds the framework.js code is slightly different and needs to be adapted.
Which platforms and devices does this affect?
Web Platform
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Add comment