不,如果你需要它,这不是一个糟糕的协议,因为它就在那里.

答案很长

官方文件说

Whether your application’s processes should be created with a large
Dalvik heap. This applies to all processes created for the
application.
It only applies to the first application loaded into a
process; if you’re using a shared user ID to allow multiple
applications to use a process,they all must use this option
consistently or they will have unpredictable results.
Most apps should
not need this and should instead focus on reducing their overall
memory usage for improved performance. Enabling this also does not
guarantee a fixed increase in available memory,because some devices
are constrained by their total available memory.

一些开发人员使用它来避免OOM的出现,所以如果你只是为了避免使用OOM,这是一个非常糟糕的问题.

Never request a large heap simply because you’ve run out of memory and
you need a quick fix. You should use it only when you know exactly
where all your memory is being allocated and why it must be retained

如果你真的需要更多空间可以使用它,你可以使用getMemoryClass()来检查堆和getLargeMemoryClass()大堆.

但是,如果您可以避免使用largeHeap,那么这将是最好的方式,因为官方文档仍在继续：

Yet,even when you’re confident your app can justify the large heap,
you should avoid requesting it to whatever extent possible. Using the
extra memory will increasingly be to the detriment of the overall user
experience because garbage collection will take longer and system
performance may be slower when task switching or performing other
common operations.
Additionally,the large heap size is not the
same on all devices and may be exactly the same as the regular heap
size. So even if you do request the large heap size,you should call
getMemoryClass() to check the regular heap size and strive to always
stay below that limit.

我还建议你看看Managing Your App’s Memory