Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
1.0.0
Issue ID
ULOG-5
Regression
No
Unity Logging throws ArgumentOutOfRangeException when logging a string formatted with an empty string parameter
Reproduction steps:
1. Open “LoggingProject“
2. Open “SampleScene“
3. Enter Play mode
Expected result: Editor is not frozen
Actual result: Editor is frozen
Reproduced in: 1.0.0-exp.7 (2022.2.17f1), 1.0.0-pre.37 (2022.2.17f1, 2023.1.0b14, 2023.2.0a12)
Could not test in: 0.51.1-preview.21 (2020.3.47f1, 2021.3.24f1) (“'Log' does not exist”), 1.0.0-exp.6 (2022.2.17f1) (“'GenerateTestsForBurstCompatibility' could not be found”)
Reproduced using: macOS 13.2.1 (Intel), Windows 11 (by reporter)
First few lines of the exception in “Editor.log”:
System.ArgumentOutOfRangeException: oldLengthBytes
This Exception was thrown from a job compiled with Burst, which has limited exception support.
#3 Unity.Logging.TextLoggerParserOutputHandlers6A45E823.Unity.Logging.WriteContextFormattedOutputw3DnKxCBzrvuRZb4Q_BjUw___0000002A$BurstDirectCall.Invoke(ref Unity.Logging.FormatterStruct formatter, ref Unity.Collections.LowLevel.Unsafe.UnsafeText hstring, ref Unity.Logging.BinaryParser mem, System.IntPtr memAllocatorPtr, ref Unity.Logging.ArgumentInfo currArgSlot) -> Unity.Logging.LogWriterUtils.ContextWriteResult_4480d00f65928b44256cd769a6d940db from Assembly-CSharp, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
Notes:
1. Also reproduced with `Log.Info()`
2. Not reproduced in Player
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
- [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
- Mouse and Pointer Events are called incorrectly in ScrollView with XRUIInputModule
- Scene view freezes when "NullReferenceException" is thrown in a .delayCall
- Memory leak occurs when repeatedly minimizing and maximizing the UI Builder window
Resolution Note:
Cannot reproduce with 2022.3.3f1 and the latest logging package "com.unity.logging": "1.0.11".