Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.2.X, 2019.3.X
Votes
0
Found in
2019.2.0a1
2019.2.18f1
2019.3
2020.1
Issue ID
1213975
Regression
Yes
Loading raw profiler data causes editor crash on pthread_kill + 10
How to reproduce:
1. Create a new project
2. Go to Window-> Analysis-> Profiler
3. Load into Profiler the "ProfilerData-2020-01-23 09-38-20 UnityWorker0.raw" file
===Crash occurs===
Reproducible with: 2019.2.0a1, 2019.2.19f1, 2019.3.0f6, 2020.1.0a21
Not reproducible with: 2017.4.36f1, 2018.4.16f1
Regressed in: 2019.2.0a1
First stack trace lines (see full stack trace in the Edit section):
0   libsystem_kernel.dylib        	0x00007fff6a4bc7fa __pthread_kill + 10
1   libsystem_pthread.dylib       	0x00007fff6a579bc1 pthread_kill + 432
2   libsystem_c.dylib             	0x00007fff6a443a1c abort + 120
3   com.unity3d.UnityEditor5.x    	0x0000000110a88491 HandleSignal(int, __siginfo, void) + 81
4   libmonobdwgc-2.0.dylib        	0x0000000148beee01 mono_chain_signal + 79
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment