Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.4.X, 2018.1.X
Votes
1
Found in
2017.3.0f3
Issue ID
986332
Regression
No
[Metal] Crash or freeze instead of error message using old asset bundle
Reproduction steps:
1. Open the attached project.
2. Open and play the LoadTest scene.
Actual behavior:
- The editor will freeze/crash.
Expected behavior:
- The editor will show an error message and moves along.
Reproduced with:
Editor, iOS
Metal
2017.3.0p2, 2018.1.0b2
Not reproducible with:
OpenGL, OpenGLES
or
2017.2.1p2
Editor Metal freeze:
WARNING: PVRTC texture format is not supported, decompressing texture
Receiving unhandled NULL exception
Obtained 10 stack frames.
iOS Metal crash:
* thread #15, name = 'UnityGfxDeviceWorker', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
* frame #0: 0x0000000100358a28 ProductName`::CreateMetalShaderShaderLab() [inlined] ExtractMetalShaderBlobDesc at MetalShaderBlobHeader.h:39 [opt]
frame #1: 0x0000000100358a28 ProductName`::CreateMetalShaderShaderLab() at GpuProgramsMetal.mm:205 [opt]
frame #2: 0x0000000100529780 ProductName`::CreateGpuProgram() at GpuProgram.cpp:883 [opt]
frame #3: 0x00000001005f317c ProductName`::DequeueAll() at GfxCreateGpuProgramQueue.cpp:33 [opt]
frame #4: 0x000000010060a68c ProductName`::RunCommand() at GfxDeviceWorker.cpp:606 [opt]
frame #5: 0x0000000100354dbc ProductName`::GfxDeviceWorkerAutoreleasePoolProxy() at GfxDeviceMetal.mm:3592 [opt]
frame #6: 0x000000010060c040 ProductName`::RunExt() [inlined] ProcessGfxCommands at GfxDeviceWorker.cpp:143 [opt]
frame #7: 0x000000010060c018 ProductName`::RunExt() at GfxDeviceWorker.cpp:345 [opt]
frame #8: 0x0000000100604314 ProductName`::RunGfxDeviceWorker() at GfxDeviceWorker.cpp:310 [opt]
frame #9: 0x00000001004f8c9c ProductName`::RunThreadWrapper() at Thread.cpp:36 [opt]
OpenGL error message:
WARNING: 281176480 format is not supported, decompressing texture
WARNING: Shader Unsupported: 'Twnkls/MobilePB/OpaquePB' - Pass '' has no vertex shader
WARNING: Shader Unsupported: 'Twnkls/MobilePB/OpaquePB' - Pass '' has no vertex shader
WARNING: Shader Unsupported: 'Twnkls/MobilePB/OpaquePB' - All passes removed
WARNING: Shader Unsupported: 'Twnkls/MobilePB/OpaquePB' - Setting to default shader.
WARNING: Shader Unsupported: 'Twnkls/MobilePB/Shadow' - Pass '' has no vertex shader
WARNING: Shader Unsupported: 'Twnkls/MobilePB/Shadow' - Setting to default shader.
Comments (9)
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
- A different Font Asset is applied when the original Font Asset is deleted while UI Builder is open
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
Peter77
Aug 11, 2018 04:50
Fixed in Unity 2017.4.9f1
https://unity3d.com/unity/whatsnew/unity-2017.4.9
SamiSdd
Jul 12, 2018 22:49
Seems Like there is something wrong with shader program. Seems to be happening with Resource.Load on Sprite. Its Related to Metal+iOS11+Multithreaded Rendering
SamiSdd
Jul 12, 2018 21:41
We're also seeing it in LTS 2017.4.6 Waiting for LTS Fix
CerberusInteractive-Morgan
May 22, 2018 17:17
Also, my asset bundles are not old, all are built in 2018.1.0f2
CerberusInteractive-Morgan
May 22, 2018 17:15
Still occurring in 2018.2.0b4 as Wisdominfotech has said :) ... This is seriously detrimental
WisdomInfotech
May 16, 2018 04:56
It's not fixed in 2018.2.0b4, please reopen this issue
andrewkw
Apr 30, 2018 13:32
You keep showing fixes being done in 2018 - but what about 2017 LTS track?
andrewkw
Apr 30, 2018 13:30
Massive issue - can not upgrade app until this fixed.
Please advise when this will be fixed
tomerpeledNG
Jan 24, 2018 07:00
I agree - it should not crash!