Search Issue Tracker
Fixed in 1.0.4
Votes
0
Found in [Package]
1.0.4
Issue ID
1300310
Regression
Yes
[Dual Screen] Profile Analyzer - Moving Editor to a different Screen aborts loading of the PA data
How to reproduce:
1. Open the attached project named "Case_1300310"
2. Open the Profile Analyzer window
3. Load the attached pdata file
4. As it is loading move the Editor to another screen
5. Observe the loading progress bar and the console window
Expected results: The data file is loaded without any errors
Actual results: A warning message is printed and the loading process is aborted
Reproducible with: 1.0.4(2019.1.0a10, 2019.4.18f1, 2020.1.17f1, 2020.2.1f1, 2021.1.0b1)
Not reproducible with: 1.0.0, 1.0.4(2018.4.30f1, 2019.1.0a9)
Notes:
1. Does not occur with 2019.4, 2020.1, 2020.2 and 2021.1 when using package version 1.0.3 or earlier
2. System.Threading.ThreadHelper:ThreadStart () message is logged in the Console window after the Editor Window is moved
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
Add comment