Search Issue Tracker
Fixed in 5.3.8
Votes
0
Found in
5.3.6f1
Issue ID
817335
Regression
No
[iOS] Crash when running on iOS Simulator with Xcode 8.0 Beta 3
To Reproduce:
1. Build and run an empty project with Xcode 8 Beta 3 Simulator (iOS).
2. Observe that on launch the app crashes, after this warning:
"Using memoryadresses from more that 16GB of memory"
in
* thread #9: tid = 0x42347a, 0x0000000102a571b8 ProductName`::AllocationPage<RequestType::kRegister>() + 270 at UnityDefaultAllocator.cpp:179, stop reason = EXC_BAD_ACCESS (code=1, address=0xabbf)
* frame #0: 0x0000000102a571b8 ProductName`::AllocationPage<RequestType::kRegister>() + 270 at UnityDefaultAllocator.cpp:179
frame #1: 0x0000000102a56d5b ProductName`::RegisterAllocation() + 93 at UnityDefaultAllocator.cpp:242
frame #2: 0x0000000102a56cd8 ProductName`::Allocate() + 80 at UnityDefaultAllocator.cpp:27
frame #3: 0x0000000102a540cf ProductName`::Allocate() + 467 at MemoryManager.cpp:1105
frame #4: 0x0000000102a54c31 ProductName`::ThreadInitialize() [inlined] malloc_internal + 47 at MemoryManager.cpp:267
frame #5: 0x0000000102a54c02 ProductName`::ThreadInitialize() [inlined] operator new at MemoryManager.cpp:134
frame #6: 0x0000000102a54c02 ProductName`::ThreadInitialize() + 106 at MemoryManager.cpp:914
frame #7: 0x0000000102c071d2 ProductName`::RunThreadWrapper() + 30 at Thread.cpp:31
frame #8: 0x000000010b1a699d libsystem_pthread.dylib`_pthread_body + 131
frame #9: 0x000000010b1a691a libsystem_pthread.dylib`_pthread_start + 168
frame #10: 0x000000010b1a4351 libsystem_pthread.dylib`thread_start + 13
3. This is not reproducible with Xcode 8.0 Beta 2 and Beta 1.
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
- [Android] FPS does not match the targeted FPS when it is set with Application.targetFrameRate
- RenderPipelineManager.activeRenderPipelineTypeChanged does not detect changes when changing the Render Pipeline Asset outside of Play Mode
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
swaroops1
Nov 29, 2016 07:02
I still see this issue
fingersbleeding
Nov 22, 2016 16:18
Issues is resolved using:
Unity 5.4.3f1
Xcode Version 8.1 (8B62)
fingersbleeding
Nov 22, 2016 15:47
Status is marked as Fixed in Unity 5.3.8, but currently experiencing this issue:
Using:
Unity 5.4.0f3
Xcode Version 8.1 (8B62)
Steps to reproduce:
Create a blank Unity project.
Build Settings:
iOS
Run in XCode as: Both Release and Debug trigger the issue
Symlink Unity Libraries: true
Development Build: true
Player Settings > Other Settings:
Scripting Backend: Ill2cpp
Target SDK: Simulator SDK
Build project. Open in Xcode.
Hit play in Xcode, Xcode will launch simulator and throw the above error for EXC_BAD_ACCESS in UnityDefaultAllocator.cpp