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
- [Android] Light2D with Light type "Spot" does not work in the Player on some Pixel devices
- [Android] Loading the asset using an old reference returns null even when the "FormerlySerializedAs" attribute is used
- Crash on ParticleSystemTrailGeometryJob::RenderJobCommon when changing trail Mode change with a large particle count
- Mouse cursor does not revert to the default mouse cursor when pressing the "Add column" button in the Search window
- ArgumentException is thrown and textures become unreadable when AssetBundle.Unload(false) is called
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'