App crash on launch library "/system_ext/lib64/libmigl.so"

Unity Engine
, ,
1

I built a game using Unity 2022.3.2, URP included, I ran the game on the phone Redmi Note 12 running MIUI 14.0.12, Android 13, I got this error and the game crashed on opening, before the Splash screen shows

library "/system_ext/lib64/libmigl.so" ("/system_ext/lib64/libmigl.so") needed or dlopened by "/system/lib/libEGL.so" is not accessible for the namespace: [name="(default)", ld_library_paths="", default_library_paths="/system/lib:/system_ext/lib", permitted_paths="/system/lib/drm:/system/lib/extractors:/system/lib/hw:/system_ext/lib:/system/framework:/system/app:/system/priv-app:/system_ext/framework:/system_ext/app:/system_ext/priv-app:/vendor/framework:/vendor/app:/vendor/priv-app:/system/vendor/framework:/system/vendor/app:/system/vendor/priv-app:/odm/framework:/odm/app:/odm/priv-app:/oem/app:/product/framework:/product/app:/product/priv-app:/data:/mnt/expand:/apex/com.android.runtime/lib/bionic:/system/lib/bootstrap"]

How do I fix it?

Longer log:

I tried another build with Unity 2022.3.8, still crash, the log is a bit different

1 Like
2

issue tracker Unity Issue Tracker - [Android] Crash "MemoryManager::VirtualAllocator::GetBlockInfoFromPointer(void const*)" when the project is built with Development Build and opening the Player

3

This still happens on Unity 2022.3.20 when I build development build

4

This doesn’t look your bug ? Since it’s about ’
MEMORYMANAGER::VIRTUALALLOCATOR::GETBLOCKINFOFROMPOINTER(VOID CONST*)’ while your stacktrace is different?

5

Happening to me too on a similar setup - mine’s a Redmi Note 13.

Regular build runs OK, development build crashes on startup.

It’s failing to open libmigl.so (Xiaomi-specific library I guess) via libEGL.so - from logcat:

library "/system_ext/lib64/libmigl.so" ("/system_ext/lib64/libmigl.so") needed or dlopened by "/system/lib/libEGL.so" is not accessible for the namespace: [name="(default)", ld_library_paths="", default_library_paths="/system/lib:/system_ext/lib", permitted_paths="/system/lib/drm:/system/lib/extractors:/system/lib/hw:/system_ext/lib:/system/framework:/system/app:/system/priv-app:/system_ext/framework:/system_ext/app:/system_ext/priv-app:/vendor/framework:/vendor/app:/vendor/priv-app:/system/vendor/framework:/system/vendor/app:/system/vendor/priv-app:/odm/framework:/odm/app:/odm/priv-app:/oem/app:/product/framework:/product/app:/product/priv-app:/data:/mnt/expand:/apex/com.android.runtime/lib/bionic:/system/lib/bootstrap"]
6

I disabled Vulkan in favor of OpenGLES3, and voila, development builds no longer crash, and the graphics performance issues (which I was going to profile) vanished.

(In Player settings (Android) > Other Settings > Rendering: uncheck Auto Graphics API, then remove Vulkan from Graphics APIs list.)

So that’s a solution for me.

1 Like
7

After making thread and seeing no reply, I reported the bug through Unity bug reporting page and they sent me a bug tracking page which has a link to that issue tracker.

8

Could I ask you to share a report number that you received? I saw reports of some similar cases and would like to investigate further. Report number should start with “IN”.

9

it was IN-53346

1 Like
10

@marta-se @cdr9042 can someone confirm if this issue was indeed fixed?
We are seeing something similar using Unity 2022.3.22, I’m wondering if it was solved.

Also, i didn’t see this ticket number in any release notes.

11

We recieved several reports with similar issues, so we initiated an investigation on what might be causing it. At the moment, our development team is trying to find out when the issue started happening. I am tracking two issue reports at the moment, and as soon as they go public, I will post them here.

2 Likes
12

Disabled Vulkan works for me. Thanks!

13

Getting a similar error with Unity 2022.3.24f1, this is the stack trace:

 Error CRASH Version '2022.3.24f1 (334eb2a0b267)', Build type 'Development', Scripting Backend 'il2cpp', CPU 'armeabi-v7a'
 Error CRASH Build fingerprint: 'Xiaomi/olivelite/olivelite:10/QKQ1.191014.001/V12.5.2.0.QCPMIXM:user/release-keys'
 Error CRASH Revision: '0'
 Error CRASH ABI: 'arm'
 Error CRASH Timestamp: 2024-06-23 13:47:38.950208675+0300
 Error CRASH pid: 28152, tid: 28553, name: UnityGfxDeviceW  >>> <REDACTED> <<<
 Error CRASH uid: 10245
 Error CRASH signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr --------
 Error CRASH Cause: null pointer dereference
 Error CRASH     r0  7cc0ea68  r1  79ec3f90  r2  7bbfc975  r3  00000010
 Error CRASH     r4  79ec3f90  r5  00000000  r6  00000000  r7  a8c89260
 Error CRASH     r8  00000001  r9  00000000  r10 00000000  r11 7bbfc975
 Error CRASH     ip  a8c87ce8  sp  5e37bc48  lr  7c5d0f50  pc  7c5f574c


libunity.so (vk::BufferResource::SetLabel(vk::smile:ebugToolsBase const*, char const*)+40) (BuildId: 41f275ed92b33086)
libunity.so (vk::ScratchBuffer::poolEntry::poolEntry(vk::BufferManager&, unsigned int, unsigned int, vk::ScratchBuffer::MemoryAccessType, bool)+252) (BuildId: 41f275ed92b33086)
libunity.so (vk::ScratchBuffer::GetPool(unsigned int)+220) (BuildId: 41f275ed92b33086)
libunity.so (vk::ScratchBuffer::ReserveImpl(unsigned int, vk::CommandBuffer*, vk::FrameNumbers const&)+904) (BuildId: 41f275ed92b33086)
libunity.so (vk::ScratchBuffer::Reserve(unsigned int, vk::CommandBuffer*, vk::FrameNumbers const&)+316) (BuildId: 41f275ed92b33086)
libunity.so (vk::ImageManager::AllocateTextureUploadBuffer(vk::CommandBuffer*, vk::ScratchBuffer*, vk::Image*, vk::ImageData const&, VkExtent3D const&, GraphicsFormat, int, core::vector<VkB
libunity.so (vk::Texture::AllocateTextureUploadBuffer(vk::CommandBuffer*, vk::ScratchBuffer*, vk::ImageData const&, VkExtent3D const&, GraphicsFormat, int, core::vector<VkBufferImageCopy, 0
libunity.so (GfxDeviceVK::AcquireTexture2DUploadMemory(TextureCreateData&, TextureUploadMemory*&)+404) (BuildId: 41f275ed92b33086)
libunity.so (AcquireTexture2DUploadMemory(GfxDevice&, TextureCreateData*, TextureUploadMemory*&)+30) (BuildId: 41f275ed92b33086)
libunity.so (AsyncTextureProcessingCompleteCallback(GfxDevice&, AsyncUploadCallbackInfo const&)+66) (BuildId: 41f275ed92b33086)
libunity.so (AsyncUploadManager::AsyncResourceUpload(GfxDevice&, int, AsyncUploadManagerSettings const&)+248) (BuildId: 41f275ed92b33086)
libunity.so (GfxDeviceWorker::RunCommand(ThreadedStreamBuffer&)+23110) (BuildId: 41f275ed92b33086)
libunity.so (GfxDeviceWorker::RunExt(ThreadedStreamBuffer&)+56) (BuildId: 41f275ed92b33086)
libunity.so (GfxDeviceWorker::Run()+102) (BuildId: 41f275ed92b33086)
libunity.so (GfxDeviceWorker::RunGfxDeviceWorker(void*)+2) (BuildId: 41f275ed92b33086)
libunity.so (Thread::RunThreadWrapper(void*)+818) (BuildId: 41f275ed92b33086)

Any news regarding that?

14

Hi all. I have an update on issues that were reported to us. Our dev team has landed a fix for 2022.3.33f1 that should resolve the issue described in this thread. Could you let us know if this helps?