I’ve only briefly tested Android.Slides so far, but simply loading a one-slide, text-only 40KB PPTX presentation on an Android emulator (AVD, Samsung Galaxy S3 API 17 profile) caused a long time of processing followed by an out of memory exception, or it also finished in another case in about 2 minutes. Here’s the code:
PresentationEx presentation = new PresentationEx(“test.pptx”, new LoadOptions(LoadFormat.Pptx));
I’ve added aspose.slides-1.1.0.jar to my Android Studio project and just put this code in my activity’s onCreate() method. Ideally I’d also like to be able to convert pptx to pdf as well, but performance is obviously an issue. I’m running the Android emulator on a newer Mac Pro, so apps run speedy in general. Thoughts?
Hi Steve,
I have observed the issue shared by you and request you to please share the heap size allocation on your end. I will investigate the issue further on my end to help you out.
Many Thanks,
Below is the full AVD profile. The heap size is 64MB, which is the standard size for a Samsung Galaxy S3, at least according to the settings in the Android Studio AVD Manager (Tools -> Android -> AVD Manager -> Create Virtual Device -> Phone -> Samsung Galaxy S3).
For what it's worth, I've also tried adding android:largeHeap="true" to my AndroidManifest.xml with the same results. It's probably just pegging and freeing memory on the heap until an OOM error, or until it finishes in other cases.
Name: Samsung_Galaxy_S3_API_17
CPU/ABI: ARM (armeabi-v7a)
Path: /Users/smellema/.android/avd/Samsung_Galaxy_S3_API_17.avd
Target: Android 4.2.2 (API level 17)
Skin: 720x1280
SD Card: 100M
Snapshot: no
hw.lcd.density: 320
hw.dPad: no
avd.ini.encoding: UTF-8
hw.camera.back: none
disk.dataPartition.size: 200M
hw.gpu.enabled: yes
runtime.network.latency: none
skin.dynamic: no
hw.keyboard.lid: yes
hw.keyboard: yes
hw.cpu.model: cortex-a8
runtime.network.speed: full
hw.device.hash2: MD5:dddf200a5d3c8658d6f8066b2e307372
hw.ramSize: 1024
tag.id: default
tag.display: Default
hw.sdCard: yes
hw.device.manufacturer: User
hw.mainKeys: yes
hw.accelerometer: yes
hw.trackBall: no
hw.device.name: Samsung Galaxy S3
hw.battery: yes
hw.sensors.proximity: yes
AvdId: Samsung_Galaxy_S3_API_17
hw.sensors.orientation: yes
hw.audioInput: yes
hw.camera.front: none
hw.gps: yes
avd.ini.displayname: Samsung Galaxy S3 API 17
snapshot.present: no
vm.heapSize: 64
runtime.scalefactor: auto
Hi Steve,
I have worked with the presentation file shared by you and have been able to observe slow performance issue on my end. I have crated an issue with ID SLIDESANDROID-28 in our issue tracking system to further investigate the issue and improve API performance. This thread has been linked with the issue so that you may be automatically notified once the issue will be resolved.
We are sorry for your inconvenience,