Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.6.0f3
Issue ID
896211
Regression
No
[WASM] profiler doesn't work with Firefox
-e: see title
--works in Canary59, tested and broken in FF53 and FF55
-repro:
--open attached project
--enable wasm, dev build & auto-connect profiler
--build&run in FF
--NOTICE profiler doesn't start profiling
--run the same in Canary
--notice profiler starts profiling
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment