Search Issue Tracker
Fixed
Votes
3
Found in [Package]
3.0.3
Issue ID
BUTFP-29
Regression
No
The "AssetDatabase.Refresh" is called by the Performance testing API package when the test script and assembly don't use anything from the performance testing API functionality
How to reproduce:
1. Open the “ReproProject“ project
2. In the Test Runner window click on Run All
3. Make changes to the “Test.cs“ script (add/delete a new line) and save them
4. In the Test Runner window click on Run All
5. Observe if Domain Reload happens
6. Add the Performance testing API package (“com.unity.test-framework.performance”)
7. Repeat the steps 3-5
Expected result: Domain Reload does not happen in both scenarios
Actual result: Domain Reload happens after adding the Performance testing API package
Reproducible with: 2.8.1-preview, 3.0.1 (2021.3.45f1, 2022.3.51f1), 3.0.3 (2021.3.45f1, 2022.3.51f1, 6000.0.25f1, 6000.1.0a2)
Reproducible on: macOS 14.6.1 (Intel), Windows 10 (Reporters)
Not reproducible on: No other environments tested
Notes:
- The Performance testing API package should automatically not run its logic when there are no tests marked with their {{PerformanceAttribute}}
- The Performance testing API package is added as a dependency when adding the Universal RP package so far in Unity 6, and it is not possible to easily disable it
- The reproduction project is using a hot-reload plugin
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Add comment