Search Issue Tracker
By Design
Votes
0
Found in
2017.3.0a1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1115544
Regression
No
PackedMemorySnapshot: Array type 'baseOrElementTypeIndex' does not point to its element type
Steps to reproduce:
1. Download attached project
2. In toolbar select BugReport > Open TestCode Window
3. Click "Capture Memory" button
Expected results: Array types should provide a baseOrElementTypeIndex to figure out its element type.
Actual results: Various array types found with the message "Array '<name>' has no element type".
Reproduced with: 2019.2.0a1, 2019.1.0a14, 2018.3.3f1, 2017.4.19f1
Rproducible with: 4.x scripting runtime
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
- [OpenGLES][XR] Zooming in on the camera's URP opaque texture causes "double vision" on Quest in OpenGLES3
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
Resolution Note (2019.2.X):
if the array of type x is declared as array<x> and initialized as new array<x> of size without any instance of x ever being created we will miss the type x during the crawling as it would not be initialized. This is expected behavior.