Open-event-droidgen: App crashing due to runtime OutOfMemory error

[harshitagupta30]

Actual Behaviour
Currently, we are using bitmap in SpeakerDetailsActivity due to which while loading a bitmap the app is raising an OutOfMemory exception at runtime.

Expected Behaviour
It should be resolved otherwise it will lead to the crash app.

Would you like to work on the issue?
Yes

[betterclever]

@harshitagupta30 Which activity is exactly causing the issue? Can you provide full stacktrace ?

[harshitagupta30]

@betterclever SpeakerDetailActivity is using bitmap to load the images. This is the complete stacktrace which was generated and this happened when I was transitioning to Speaker's Detail.

[m-murad]

@harshitagupta30
I didn't face the issue.
what device are you using?

[arp95]

@harshitagupta30
this is device specific i think. I didnt face the issue.

[betterclever]

@arp95 @free4murad It is due to the fact that genymotion emulator has less default heap size for apps which is being used for testing. The app might crash in a similar low ram device.

@harshitagupta30 I think a better approach would be to reduce image size before applying than asking for more heap in Manifest , image size can be reduced after Bitmap is ready in Picasso using custom transformer.
That way less memory will be consumed.
Refer this: http://stackoverflow.com/questions/23740307/load-large-images-with-picasso-and-custom-transform-object

[harshitagupta30]

@betterclever The ram size of the emulator is currently 2 GB which I think is sufficient enough. Also, as far as I know we are using bitmap images only in some case where we need to draw the Speaker's image not when downloading an image. Still, I'll try to solve it in the way described in link. Thanks for the suggestion. :+1:

[betterclever]

@harshitagupta30 It doesn't depend on RAM size but heap size of emulator. Check build.prop of emulator for that. If your emulator has less heap, then it will crash irrespective of RAM size. I faced a similar issue on my app once. Stock emulator provides option to change heap size, AFAIK genymotion doesn't.

Secondly, we are using Bitmap there to dynamically get accentColor from the image using the Palette Class from Support Design Library, which needs to use the Bitmap resource to extract color. Scaling down should optimize it. 👍

[harshitagupta30]

@betterclever Thanks! I was not aware of this. :clap: :+1:

[betterclever]

@harshitagupta30 following suggestions on #1264, scaling down on phone won't be required. This may be left therefore.