Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.2.0a4
2017.2.0f3
Issue ID
1014360
Regression
Yes
[Mac] Built application crashes on ApiGLES::BindFramebuffer when graphics API is set only to Metal
How to reproduce:
1. Open the user's attached "iValtech.zip" Unity project.
2. Build Mac Standalone program and run it.
Expected result: The built application will run without crashing.
Actual result: The built application crashes after opening it.
Reproducible with: 2017.2.0a4, 2017.2.2p2
Not reproducible with: 5.6.0a1, 5.6.5p3, 2017.1.3p2, 2017.2.0a3, 2017.3.2f1, 2017.4.0f1, 2018.1.0b13, 2018.2.0a6
Note:
First stack frame in the Player.log:
#0 0x0000000037e656 in ApiGLES::BindFramebuffer(gl::FramebufferTarget, gl::Handle<(gl::ObjectType)9>)
The crash happens even when building a single new empty scene in the project. The crash seems to be related to corrupted "Library" folder. Deleting "Library" folder fixes the issue. Another workaround is setting "Auto Graphics API for Mac" to true in player's settings.
Fixed in 2017.3.0a1 version.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Add comment