Search Issue Tracker
Won't Fix
Votes
1
Found in
5.5.1f1
Issue ID
892260
Regression
No
Assertion logs in release build with ForceEnableAssertions are missing some stack frames
Steps to reproduce:
1. Open the project attached
2. Build it on Standalone with developer mode enabled
3. Run the built application
4. Press button "1"
5. Observe the text on the application
Results: a stack trace generated by user's custom class is generated first, followed by stack trace of Unity, called by OnLogMessageReceivedThreaded(string, string, LogType)
OnLogMessageReceivedThreaded has fewer stack frames than the custom class (see attached "image1.PNG")
Expected: stack traces are the same.
Reproduced on versions: 5.5.2p2, 5.6.0f1, 2017.1.0a3
Reproduced using: iPhone 7 iOS 10.1, Xcode 8.3 beta; Samsung Galaxy S6 Edge, Android 6.0.1, macOS 10.12
Notes:
Could not reproduce on: 5.4.5f1 (can't downgrade)
User has created Editor script for building to iOS and Android with ForceEnableAssertions flag. Use it for testing on iOS/Android builds
On android build the stack trace returned by OnLogMessageReceivedThreaded(string, string, LogType) is completely empty, while user's custom class returns the same path as in iOS
Comments (5)
-
Deepscorn
Sep 09, 2017 23:50
I did some more tests and found out, that not only Assert.IsFalse may lose frames, but even exception caught by Unity Framework may be reported with missing frames too. I tested in both editor and android device release build: http://deepscorn.blogspot.ru/2017/05/why-unity-may-lose-frames-in-stacktrace.html
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
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
- FrameTimingManager.GetLatestTimings adds background time to the next focused frame when the Player is unfocused
- PropertyDrawer gets disposed while still being active when adding a secondary component
- Realtime GI behaves differently when using Unlit (Amplify) and Lit (Shader Graph) shaders in URP
- API Updater strips Unity-owned Custom Attribute references within precompiled DLLs
Resolution Note:
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this fix for the time being. We understand that this will cause problems for some users, and so may address in a future version.