Search Issue Tracker
By Design
Votes
0
Found in
4.3.0f4
Issue ID
576153
Regression
Yes
Android apps made with Unity 4.3 takes about twice more space on device than before
An empty Unity project built with Unity 4.2 takes about 8MB of device memory once it is installed, however the same project built with Unity 4.3 takes about 22MB. This is only reproducible when the development build option is not enabled in the build settings.
Reproduced on:
Google Nexus 4 with Android 4.3
Reproduced with:
Unity Version 4.3.0f4 (e01000627d60)
Resolution:
Since Unity 4.3 we let android unpack our native libraries on the device which makes the application start faster and lets the OS cache our libraries. Just to be clear - the increase in size should be constant and it should not be affected by c# libraries or content put into the project.
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
- [iOS] App crashes when trying to use WebCamTexture depth data on back triple camera
- [Mobile] Only second base Camera out of two base Cameras with priority 1 and -1 is rendered in the Player
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
MedichloriANR
Jul 31, 2014 19:52
A project upgraded from Unity 4.2 to Unity 4.3 is much more likely to crash or cause ANR from the fact that the installed application file size is more than doubled. I don't see how a single digit percentage improvement in application load time on some devices justifies introducing crashes and ANRs to a project that ran perfectly fine (performance-wise) under unity 4.2 to a broad range of mid or low level devices. Essentially, you have allegedly designed the fact that responsible developers are having to block support for a number of devices that are just a couple or few years old. The hardware affected by the bloat in this case for projects I've alluded to happens to comprise roughly 1/3 of the installed user base for those apps.
I would like to know if there are any options available to circumvent this "feature".