Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.1f1
Issue ID
929861
Regression
No
Crashed in :mono_custom_attrs_from_class while importing object data
Steps to reproduce:
1) Download attached project 'BugRepro.zip' and open in Unity
2) In Project window, open 'Maniac Manfred.articyu3d file' with any text editing program(to reproduce I've used 'Notepad++')
3) Rename 7th line ending from '....7A19' to '......7A18'
4) Save it and focus back on Unity
5) Receive a crash while Unity importing object data:
========== OUTPUTING STACK TRACE ==================
0x00007FFCCCD78F5A (mono) [c:\buildslave\mono\build\mono\metadata\reflection.c:8394] mono_custom_attrs_from_class
0x00000001409179A5 (Unity) scripting_class_has_attribute
0x00000001409824E8 (Unity) PersistentManager::IsObjectNonTextSerialized
0x000000014098DB37 (Unity) PersistentManager::WriteFile
0x0000000141BE1A97 (Unity) AssetDatabaseV1::WriteSerializedAsset
0x0000000141BE1E20 (Unity) AssetDatabaseV1::WriteSerializedAssets
0x0000000141BA7725 (Unity) AssetDatabase::SaveAssets
Reproduced with:
5.5.4p2, 5.6.2p3, 2017.1.0f3, 2017.2.0b2
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
- Memory leak when a lot of UI elements are spawned and despawned
- Warnings are not logged in the Console window when using external code analyzers
- Errors “TLS Allocator ALLOC_TEMP_TLS, underlying allocator ALLOC_TEMP_MAIN has unfreed allocations, size 288“ appear constantly when Prefab is open
- Crash on PPtr<Shader>::operator or NullException errors spammed in console when calling Dispose() on null GraphicsBuffer with baked Reflection Probes
- “EndRenderPass: Not inside a Renderpass” and other Render Graph errors in the Player when Render Graph is enabled and Overlay UI is used
Resolution Note (2019.1.X):
Hi there,
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
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.
Unity QA Team