Search Issue Tracker
Won't Fix
Votes
8
Found in
5.3.0f4
Issue ID
763225
Regression
No
[iOS] Application crashes while allocating memory for texture
Steps to reproduce:
1. Open attached project (mprotectBug_stripped.zip)
2. Build for iOS
3. Build the Xcode project and run on device
4. Click 'Animation' button to enable gif playback
5. Click right or left arrow several times to load new textures
6. Notice the application eventually crashes with the following error:
Mprotect failed at 0xed50000 (length 212992) with errno 12
Mprotect remapping failed
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
- Pickers and ‘+'/’-' buttons are not visible on the right side of parameter fields when the width of the "Project Settings... -> Quality" window is small
- "AssertionException: Assertion failure. Value was False" error is thrown when unmaximizing a docked UI Builder Window
- INVALID_ENUM warning is thrown in WebGL Player when building an empty scene
- Crash on ApiGLES::ClearBufferSubData when running the Player a second time on Meta Quest 2
- "Process VFXCamera Command" column is displayed in the "Render Graph Viewer" when there are no VFX in the Scene
shixuesi
Jul 18, 2016 10:41
I got fix this problem。I change the Scripting Backend to IL2CPP。
povilas
Mar 01, 2016 16:12
If anyone can repro the bug on il2cpp, please submit bugs and shout on forums.
povilas
Mar 01, 2016 16:11
An excerpt from an email sent to the reporter. This should clarify the reason for the bug closure.
"
It is a complex failure of internal memory allocation routines deep within mono runtime. The bug is known to mono developers, however even them could not fix it[1]: they just disabled memory retrieval via mmap. Since this means that mono can't return allocated memory to the OS, we can't use the same workaround.
You can use either of the following two workarounds:
- either use il2cpp scripting backend, which does not seem to have this problem -- at least we could not reproduce it.
- refrain from excessive number of allocations.
If you are able to reproduce this issue on il2cpp, don't hesitate to reply, we'll investigate the bug further.
[1]: https://bugzilla.novell.com/show_bug.cgi?id=504411
"