iOS Build Environment Help Center

Delete

(Leave this as-is, it’s a trap!)

To delete this post you must be either the original author or a designated moderator.
The content of the post will be removed but the name and date will remain.

  • The post will be removed completely from the thread, rather than blanked
  • Only posts on the last page of the thread can be removed completely (so as to not break permalinks)

RE[7]: Getting crash upon app launch. Remote debugger not providing useful information

Pierre-Marie Baty

Wow. Strange choice by Unity here. I hope the benefits of these inflated memory requirements were well worth their expense.

Good luck in optimizing all that…

:: @Pierre-Marie Baty added on 20 May ’22 · 06:53

*edit* as I understand it it’s not Unity’s fault but rather Apple that ditches OpenGL further and attempts to force everyone to use Metal-specific ways of coding, resulting in less portable code. I think the Unity engine could improve their memory usage at the expense of a big rewrite, which they’re probably reluctant to do because it would involve maintaining a large branch of very OS-specific and non portable code.

Moderators: Pierre-Marie Baty