Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.67f1
6000.3.9f1
6000.4.0b9
6000.5.0a7
Issue ID
UUM-134407
Regression
No
Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
Reproduction steps:
1. Create a new project
2. Edit > Project Settings… > Graphics
3. Enter large number in Preloaded Shaders field (e.g. “999999999”)
4. Observe the Editor
Actual result: Editor crashes
Expected result: Editor doesn’t crash
Reproducible with: 6000.0.67f1, 6000.3.9f1, 6000.4.0b9, 6000.5.0a7
Reproduced on: macOS Sequoia 26.2 (M4), Windows 11
Note:
- Issue is also reproducible with Always Included Shaders field
- First few lines of Stack Trace:
{code:java}
Obtained 56 stack frames.
#0 0x000001959fb508 in _platform_memmove
#1 0x00000103fb43a8 in ResizeArrayGeneric(TypeTreeIterator const&, core::vector<unsigned char, core::allocator<unsigned char, 0ul>>&, int, int, bool, SerializedManagedReferencesIndex, TypeTree const)
#2 0x0000010414ebc0 in SerializedProperty::ResizeArray(int)
#3 0x0000010415713c in SerializedProperty::SetIntValue(long long)
#4 0x00000382d34bc8 in (wrapper managed-to-native) UnityEditor.SerializedProperty:SetIntValueInternal_Injected (intptr,long) [{0x9934ae2b0} + 0x68] (0x382d34b60 0x382d34c20) [0x17a7c2a80 - Unity Child Domain]{code}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
- UnityEvent does not get pasted to a uGUI component when trying to copy it from a Script
Add comment