Search Issue Tracker
Fixed
Fixed in 6.1.1
Votes
0
Found in [Package]
6.1.1
Issue ID
XRVRT-40
Regression
Yes
VR Template Crash on "MemoryManager::Allocate()" when switching Platform to Android in Build Profiles
Reproduction steps:
1. Create a new VR template project
2. In the Build Profiles, switch platform to Android
3. Observe the result
Expected result: Platform is switched for the project
Actual result: Editor crashed
Reproducible in: 6.1.1 (2022.3.1f1, 2022.3.7f1)
Not reproducible in: 6.1.1 (2022.3.0f1), 9.1.0 (2022.3.59f1 6000.0.40f1, 6000.1.0b9, 6000.2.0a6)
Fixed in: 6.1.1 (2022.3.8f1)
Reproducible on: macOS 15.3.1 (M1 Pro)
Not reproducible on: No other environments tested
Note: Regression is in the Editor version and not in the package itself
First few lines of the stack trace:
{noformat}#0 0x00000104f74c5c in MemoryManager::Allocate(unsigned long, unsigned long, MemLabelId const&, AllocateOptions, char const, int)
#1 0x00000104f74340 in malloc_internal(unsigned long, unsigned long, MemLabelId const&, AllocateOptions, char const, int)
#2 0x0000010546b9b8 in keywords::LocalKeywordState::Resize(unsigned long)
#3 0x0000010547c798 in ShaderLab::Program::GetMatchingSubProgram(Shader const, ShaderLab::Pass const, keywords::LocalKeywordState const&, unsigned int, keywords::LocalKeywordState, ShaderSnippetResult&, AsyncShaderCompilationMode, bool, int, int) const
#4 0x000001054876d4 in ShaderLab::ShaderState::FindSubProgramsToUse(Shader const, ShaderLab::Pass const*, ShaderLab::SubPrograms&, ShaderPassContext const&, keywords::LocalKeywordState const&, bool, int, int) const{noformat}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment