Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.22f1
2022.2.13f1
2023.1.0b10
2023.2.0a8
Issue ID
UUM-31724
Regression
Yes
[Linux][Mono] Crash on mono_exception_walk_trace when entering the Play Mode
Reproduction steps:
1. Open the attached “CrashRepro” project
2. Open the “/Assets/LuaTest.cs” Script File and change the scriptName variable to the full path of “/Assets/file.lua” file
3. Save and close the Script File
4. Enter the Play Mode
Expected result: Unity Editor enters the Play Mode
Actual result: Unity Editor crashes
Reproducible with: 2021.2.0a18, 2021.2.19f1, 2021.3.22f1, 2022.2.13f1, 2023.1.0b10, 2023.2.0a8
Not reproducible with: 2020.3.46f1, 2021.2.0a17
Reproducible on: Ubuntu 22.04
Not reproducible on: Windows 10 Pro 22H2
First lines of the stack trace:
#0 0x005566769c04cc in burst_signal_handler(int, siginfo_t*, void*)
#1 0x007fd484e42520 in __sigaction
#2 0x007fd2a68ba48f in mono_exception_walk_trace
#3 0x007fd2a68bb929 in mono_exception_walk_trace
#4 0x007fd2a68bc7f6 in mono_debugger_run_finally
#5 0x007fd2a68bbc93 in mono_debugger_run_finally
#6 0x007fd2a690ffed in mono_breakpoint_clean_code
Comments (1)
-
ux_liuxing
Oct 14, 2024 09:46
What is the work around ?
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
- “Asset X has no meta file, but it's in an immutable folder. The asset will be ignored.” errors are thrown when importing package with files not listed in package.json's "files" property
- There is no way to adjust the HDR Paper White value of the Unity Editor's interface, making it difficult/uncomfortable for some developers to work on very dark/bright scenes in HDR
- Animator window has a dropdown button that throws “MissingReferenceException” error on a new project when the previous project had a GameObject with an animation
- Animator State name overflows outside the visual box when the State has a long name
- UI Document file remains marked as Dirty after Undoing made changes
Resolution Note:
We don't plan to correct this issue. The submitter has a work around for it.