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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment