Search Issue Tracker
Fixed
Won't Fix in 2022.3.X, 6000.0.X, 6000.3.X
Fixed in 6000.2.X, 6000.4.0b4, 6000.5.0a4
Votes
0
Found in
2022.3.63f1
6000.0.51f1
6000.1.8f1
6000.2.0b6
Issue ID
UUM-109364
Regression
No
Generic methods with [HideInCallstack] are present when “Strip logging callstack“ option is enabled in the Console Window
Reproduction steps:
1. Open the attached “IN-104937_My project.zip“ project
2. In the Console window’s options (3 vertical dots), enable the “Strip logging callstack“ option
3. Select the “Test > Click Me“ option from the Menu Bar
4. In the Console’s options menu (3 vertical dots), enable the “Strip logging callstack“ option
5. Select the “Inspect my stacktrace!“ log inside the Console
6. Observe the stacktrace
Expected result: The generic [HideInCallstack] “ThisShouldBeHiddenButIsnt<T>()” method is hidden
Actual result: “TestLog:ThisShouldBeHiddenButIsnt<int> () (at Assets/TestLog.cs:16)“ is present in the stacktrace
Reproducible with: 2022.3.63f1, 6000.0.51f1, 6000.1.8f1, 6000.2.0b6
Reproducible on: Windows 11 (User’s platform), M1 Max MacOS 15.5 (Tested by CQA)
Not reproducible on: No other environment tested
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
- Progress indicator in Meta Quest Build Profile configuration is barely visible
- Slightly transparent objects disappear completely in Web Player when using RenderGraph
- Visual Scripting Components are hidden behind a throbber when Multiplayer Play Mode is running with at least one local instance
- Video Player does not throw an error when playing a video with unsupported encoding settings
- Errors indicating that TMP Extras were not Imported logged when opening the Render Pipeline Converter Window while in Play Mode
Resolution Note (fix version 6000.4.0b4):
Fixed in 6000.4.0b4
Resolution Note (6000.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.0.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (2022.3.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.