Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
1
Found in
4.5.1f3
Issue ID
616244
Regression
No
Internal compiler error when trying to construct a dictionary of generic struct<T,T>
To Reproduce:
1. Open the attached, notice that as long as this line:
'new Dictionary<p<object, object>, object>();'
exists in any script in the project, and 'p' is a <T,T> struct, 'Internal compiler error' will be thrown and the stack will be outputted, it will end with:
'Got a SIGSEGV while executing native code. T'
2. Only happens with structs and Dictionaries if p is changed into a class and/or dict to a list, a HashSet or other generic collection the code is compiled and executed without any issues.
Comments (1)
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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
sejton
Mar 27, 2015 08:37
I created a Point<T> generic structure and just declaring a dictionary Dictionary<Point<int>, int> induces this unexpected bug.
I don't get any internal compiler error written in Unity 5. Instead, I get a window saying mono.exe has stopped working. So, compiler has obviously crashed and when I press play button Unity logs that I have to fix compiler errors. It doesn't log which compiler errors have happened. It just logs an empty error message = empty string marked with error flag.