Search Issue Tracker
Fixed in 0.7.0
Votes
3
Found in [Package]
0.4.0-preview.10
Issue ID
1204977
Regression
No
[Entities] Unity silent crash when converting a GameObject with GenerateAuthoringComponent attribute
How to reproduce:
1. Open the user-submitted project
2. Open the Sample Scene
3. Enter Play mode
4. Observe the crash
Reproducible with: Unity 2019.3.0f4 and 2020.1.0a17 (0.2.0-preview.18, 0.3.0-preview.4, 0.4.0-preview.10) -- when compiling in debug mode.
Notes:
The issue is not reproducible prior to Unity 2019.3.0b10 because affected package versions are not available.
-------------------------------------------
Workaround:
The asmdef that contains the generated authoring component needs to have at least one class with one method.
E.g.: class SomeClass { void SomeMethod() { } }
This is due to a bug that causes Debug C# compilation not to generate method tables in the PDB file in this case. Adding one class with one method works around the issue.
Fixed in next version of Entities (0.7.0)
Comments (3)
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
- Inspector window flickers when a selector is created using a Style Class List Section
- [iOS] "UnityBatchPlayerLoop()" causes a freeze in the iOS application when it is put to the background and brought back to the foreground
- "Perform Selected" of Shortcut Manager window does not perform the shortcut in some cases
- Crash on mono_get_hazardous_pointer when running Play Mode tests in a specific project
- [iOS] ‘확인’(Done) and '취소'(Cancel) text is displayed as '...' in the on-screen keyboard when the System preferred language is set to Korean
Zagule
Mar 06, 2020 14:49
Would be great to apply the solution also for 2D Entities, where it still crashes (as of version 0.22) unless using the workaround
msfredb7
Jan 28, 2020 21:26
Edit: I don't think Visual Studio was the issue after all. My Unity 2020.1 now only seems to crash if I put it in Debug Mode (new debug mode that was added at the bottom right of the Editor)
msfredb7
Jan 28, 2020 21:22
I think I encountered the same issue. If you even encounter it again in 2020.1 (like me), try restarting visual studio. That's what seemed to have fixed it for me.