experiment with android:largeHeap=true in manifest

[pmoor]

According to http://developer.android.com/guide/topics/manifest/application-element.html this may help with memory pressure:

android:largeHeap
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.

To query the available memory size at runtime, use the methods getMemoryClass() or getLargeMemoryClass().

I have a repository I consistently fail to clone on most of my devices (only works on the N4). I know I shouldn't have large files in it, but it's just very convenient ;-) Would be awesome if you could give largeHeap a try to see if it improves things.

thank you,
patrick

[rtyley]

Hey, I wasn't aware of that manifest option, thanks for letting me know!
I'm moving house today, I'll try to get a release out in a few days time...
On 19 Dec 2013 00:15, "Patrick Moor" notifications@github.com wrote:

According to
http://developer.android.com/guide/topics/manifest/application-element.htmlthis
may help with memory pressure:

android:largeHeap
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.

To query the available memory size at runtime, use the methods
getMemoryClass() or getLargeMemoryClass().

I have a repository I consistently fail to clone on most of my devices
(only works on the N4). I know I shouldn't have large files in it, but it's
just very convenient ;-) Would be awesome if you could give largeHeap a try
to see if it improves things.

thank you,
patrick

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/99
.

[pmoor]

Yay! Thanks for the build! I was able to clone my repo on the Moto X!

[rtyley]

Yay! Thanks for the build! I was able to clone my repo on the Moto X!

Brilliant! That's good to know - thanks again for pointing out the option 👍