Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
Out of Memory on Android
Just sharing some advice about memory issues in Android.
I was getting "out of native memory" errors from the android Java VM.
My specific problem was that I was instantiating a lot of objects, each with their own loadImage() call. This was eating up all my memory and causing a crash whose cause wasn't apparent until I moved my project over to Eclipse which automatically reveals more detailed debug logging from Android and the use of memory examination tools with the MAT addon.
Remember that each image you load requires this many bytes: (width in pixels)(height in pixels)(4 bytes/pixel) of memory for the uncompressed bitmap. This can add up quite quickly in the restricted memory of Android.
So basically, use loadImage() as sparingly as possible. If you are using the same image in multiple objects, load it once at the global, sketch level, and then pass a reference to the image when you instantiate your objects.
Hopefully this will save someone the two weeks of hair pulling I just went through.
PS: this is a good resource for importing a Processing project into Eclipse: http://blog.onthewings.net/2013/04/25/setting-up-a-processing-android-project-in-eclipse/