Search Issue Tracker
Fixed in 2022.2.X
Duplicate in 2021.3.X
Votes
0
Found in
2021.2.0a4
2021.2.3f1
2022.1.0b1
Issue ID
1383511
Regression
Yes
[iOS] Crash when launching Build with "Autoconnect Profiler" enabled with the Profiler window closed
Reproduction steps:
1. Open the attached project "Case_1383511.zip"
2. Set "Run in Xcode as" to "Debug" and enable "Autoconnect Profiler" in the Build Settings
3. Build the project
4. If the Profiler window is open, close it
5. Deploy the Project to a device
6. If the crash does not occur, kill the Application and repeat from step 5
Reproducible with: 2021.2.0a4, 2021.2.4f1, 2022.1.0a16
Not reproducible with: 2019.4.33f1, 2020.3.23f1, 2021.1.0a10
Could not test with: 2021.2.0a1 (version fails to install properly), 2021.2.0a2, 2021.2.0a3 (Unrelated crash prevents testing)
Reproduces on:
- iPhone 12 Mini (iOS 14.1)
- iPhone 13 (iOS 15.0)
- iPad Air 4th Gen (iOS 14.7.1)
Does not reproduce on:
- iPhone 6 (iOS 12.4.8)
First lines of possible stack traces:
- thread #7, name = 'Profiler.Dispatcher', stop reason = EXC_BAD_ACCESS (code=2, address=0x110990000)
- frame #0: 0x00000001f3b50b70 libsystem_platform.dylib`_platform_memmove + 288
frame #1: 0x0000000108d0de24 UnityFramework`profiling::DispatchStream::WritePendingBuffers() + 104
frame #2: 0x0000000108d0c554 UnityFramework`profiling::Dispatcher::WritePendingBuffers() + 52
- thread #15, name = 'UnitySocketWriter', stop reason = signal SIGABRT
- frame #0: 0x00000001ba1749c4 libsystem_kernel.dylib`__pthread_kill + 8
frame #1: 0x00000001f3b5f434 libsystem_pthread.dylib`pthread_kill + 268
frame #2: 0x000000018e523f64 libsystem_c.dylib`abort + 164
Notes:
- Usually crashes when first launching the App, however, sometimes requires a second launch
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
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
- Shader error and warnings thrown when setting HDRP as an Active Target in Blank Shader Graph
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a5