Search Issue Tracker
Not Reproducible
Votes
0
Found in
2019.4
2019.4.13f1
2020.1
2020.2
2021.1
2021.2
Issue ID
1287190
Regression
No
[iOS] Application crashes when making a web request and using deep profiling with a "EXC_BAD_ACCESS" error
Reproduction steps:
1. Download and open the attached "DeepProfilingIssues" project
2. In the Build Settings window, switch to the iOS platform
3. Enable "Autoconnect Profiler" and "Deep Profiling Support"
4. Build and deploy the project
5. In the Editor window, open the Profiler window
6. In the Profiler window, switch the profiling target to your device and enable "Deep Profile"
7. On your device, press the button
Reproducible with: 2019.4.17f1, 2020.1.17f1, 2020.2.1f1, 2021.1.0b1, 2021.2.0a2
Could not test with: 2018.4 (Deep Profiling is not available)
Reproduced with: iPhone 12 Mini (iOS 14.1), iPhone 12 Pro (iOS 14.2.1), iPhone 6S (iOS 13.3.1)
Could not reproduce with: macOS Catalina 10.15.7, Nokia 7 Plus, Android 10, CPU: Snapdragon 660, GPU: Adreno (TM) 512
Note: from 2020.2 and up, the application doesn't crash but throws a "WebException" error in the console instead
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2021.2.X):
The WebException I could get was actually a message from exception in player that got also sent to Editor, and in my case it was a proper failure because I forgot to turn Wi-Fi on. Once I enabled Wi-Fi in iPhone, I started getting a debug message with reply from server. So, I conclude that in latest trunk everything works fine.
For versions where the crash occurrs, the fix could be searched for and backported. Either way, I suspect this issue is not mobile specific, but rather profiler or scripting issue.