Search Issue Tracker
By Design
Votes
0
Found in
2020.1.0a4
Issue ID
1183714
Regression
Yes
[Mono] [Coverage] "mono_profiler_get_coverage_data" returns wrong data
How to reproduce:
1. Open "mono_profiler_coverage_wrong_data.zip" project
2. Enable Code Coverage (Preferences > General > Enable Code Coverage)
3. Restart Unity
4. Open Test Runner (Window > Test Runner)
5. Run 'EditorTests > Tests > SequencePoints_HaveExpectedLinesAndColumns' test
Actual Result: Test fails in all asserts returning wrong values.
Expected Result: Test passes.
Reproducible with: 2020.1.0a4.
Regression introduced in: 2020.1.0a4
Not reproducible with: 2020.1.0a3, 2019.3.0b3, 2019.2.6f1.
Notes:
- Coverage doesn't exist in Unity 2019.1 and lower.
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
This is due to the new "No cost" editor attaching. Things work correctly once the Editor is switched to run with debug symbols/info.
You can switch to debug mode in the Editor (bottom right corner, press the Bug icon -> "Switch to debug mode") or by setting 'CompilationPipeline.codeOptimization = CodeOptimization.Debug'