Search Issue Tracker
Fixed
Votes
0
Found in
5.4.0b24
Issue ID
811553
Regression
No
Initializing const with non constant variables throws error message but does not link to script
1. Open my attached project
2. Open bug.unity scene.
Notice Unhnandled exception error message popping in console.
3. Try to double click on error message
Notice that nothing happens.
Expected behavior: double clicking on error message points to broken script
Actual behavior: Double clicking on error message does not do anything.
This Unhandled exception has been raised because const integer constmesh was initialized with non const array member, which values has been accessed by also using non const variables. (line 31 of sadscript.cs)
Basically:
int a = 1, b = 3;
const int constmesh = mesh.triangles[a + b];// is broken
const int constmesn = mesh.triangles[1 + 3];// is working fine.
Repro on: 5.4.0b24, 5.4.0b13, 5.3.5p7, 5.2.0f3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment