Program Crashes

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open document
2. Pinch-zoom/unzoom same page repeatedly (3-4 times)

What is the expected output?
I would expect to see the same portion of the page zoomed in and zoomed out, 
possibly faster after the first cycle due to bitmap caching.

What do you see instead?
After three to four repetitions, the viewer crashes silently and returns to the 
Browser or Library Activity. Sometimes, I get an ANR or FC.

Currently, I get the crash on the first zoom-out.

What version of the product are you using?
1.5.0 downloaded here

On what operating system?
Android (Kindle Fire) 2.3.4

What device are you using?
Amazon Kindle Fire

Please provide any additional information below.
The zoom performance of this latest version is very disappointing, as noted in 
another issue. Us users of multi-core devices (dual-core and quad-core) were 
expecting more. 
It would be EXTREMELY helpful to have a wiki page addressing the various 
performance settings, so we can make informed changes to them, rather than 
guessing what they might do.

Original issue reported on code.google.com by ugra...@323go.com on 22 Aug 2012 at 2:46

[GoogleCodeExporter]

08-22 14:00:08.513: E/EBookDroid.BitmapManager(14890): Used: BitmapRef [id=113, 
name=[471:471]:8:[0, 0], width=128, height=128, size=32768]
08-22 14:00:08.513: E/EBookDroid.BitmapManager(14890): Used: BitmapRef [id=592, 
name=[478:478]:14:[1, 4], width=128, height=128, size=32768]
08-22 14:00:08.513: E/EBookDroid.BitmapManager(14890): Used: BitmapRef [id=115, 
name=[471:471]:8:[0, 2], width=128, height=128, size=32768]
08-22 14:00:08.513: E/EBookDroid.BitmapManager(14890): Used: BitmapRef [id=785, 
name=[472:472]:8:[6, 3], width=128, height=128, size=32768]
08-22 14:00:08.536: E/EBookDroid.BitmapManager(14890): DecodeService 
OutOfMemoryError: Bitmaps&NativeHeap : 19557600(433 used / 1 
pooled)/36426264/40357888

Original comment by ugra...@323go.com on 22 Aug 2012 at 7:02

[GoogleCodeExporter]

I plugged the device to my ADB console and got the log above. It now crashes 
almost immediately when revisiting a recent book which has a high zoom level, 
making the app entirely unusable.

Original comment by ugra...@323go.com on 22 Aug 2012 at 7:04

[GoogleCodeExporter]

08-22 14:05:29.247: E/EBookDroid.BitmapManager(15142): DecodeService 
OutOfMemoryError: Bitmaps&NativeHeap : 47185920(1441 used / 0 
pooled)/62149640/70656000
08-22 14:05:29.271: E/EBookDroid.BitmapManager(15142): DecodeService 
OutOfMemoryError: Bitmaps&NativeHeap : 47185920(1441 used / 0 
pooled)/62149640/70656000
08-22 14:05:29.271: E/EBookDroid.BitmapManager(15142): DecodeService 
OutOfMemoryError: Bitmaps&NativeHeap : 48264720(1441 used / 0 
pooled)/62149640/70656000

Original comment by ugra...@323go.com on 22 Aug 2012 at 7:05

[GoogleCodeExporter]

how many pages kept in memory?
is bitmap reusing is switched on?
is bitmap allocation hack is switched on?
is using native graphics is switched on?

how many memory does your device provide for application heap? pls provide 
application info which written in log when application is started.  

Original comment by Alexander.V.Kasatkin@gmail.com on 22 Aug 2012 at 8:54

• Changed state: Discussion

[GoogleCodeExporter]

08-22 15:40:23.090: I/EBookDroid(17354): EBookDroid (org.ebookdroid) 
v1.5.0(1500)
08-22 15:40:23.090: I/EBookDroid(17354): Root             dir: /system
08-22 15:40:23.090: I/EBookDroid(17354): Data             dir: /data
08-22 15:40:23.090: I/EBookDroid(17354): External storage dir: /mnt/sdcard
08-22 15:40:23.090: I/EBookDroid(17354): App      storage dir: 
/mnt/sdcard/.org.ebookdroid
08-22 15:40:23.090: I/EBookDroid(17354): Files            dir: 
/data/data/org.ebookdroid/files
08-22 15:40:23.090: I/EBookDroid(17354): Cache            dir: 
/data/data/org.ebookdroid/cache
08-22 15:40:23.090: I/EBookDroid(17354): VERSION     : 10
08-22 15:40:23.090: I/EBookDroid(17354): BOARD       : omap4sdp
08-22 15:40:23.090: I/EBookDroid(17354): BRAND       : generic
08-22 15:40:23.090: I/EBookDroid(17354): CPU_ABI     : armeabi-v7a
08-22 15:40:23.090: I/EBookDroid(17354): CPU_ABI2    : armeabi
08-22 15:40:23.090: I/EBookDroid(17354): DEVICE      : D01E
08-22 15:40:23.090: I/EBookDroid(17354): DISPLAY     : 
L27.12.1-P1_QUANTA_20110422_quantaonly-1131-g6a76ea4
08-22 15:40:23.090: I/EBookDroid(17354): FINGERPRINT : 
generic/blaze/blaze:2.3.4/GINGERBREAD/6.3.1_user_4107720:user/release-keys
08-22 15:40:23.090: I/EBookDroid(17354): ID          : GINGERBREAD
08-22 15:40:23.090: I/EBookDroid(17354): MANUFACTURER: TI
08-22 15:40:23.090: I/EBookDroid(17354): MODEL       : Kindle Fire
08-22 15:40:23.090: I/EBookDroid(17354): PRODUCT     : blaze
08-22 15:40:23.090: I/EBookDroid(17354): Debug logging disabled by default
08-22 15:40:23.145: I/EBookDroid.VMRuntimeHack(17354): VMRuntime hack 
initialized!
08-22 15:40:23.145: I/EBookDroid.VMRuntimeHack(17354): No heap preallocation

how many pages kept in memory? 0
is bitmap reusing is switched on? YES
is bitmap allocation hack is switched on? YES (it's MUCH WORSE when off)
is using native graphics is switched on? YES

Original comment by ugra...@323go.com on 22 Aug 2012 at 8:57

[GoogleCodeExporter]

Also, it crashes on Google Nexus 7, but not nearly as quickly.

Original comment by ugra...@323go.com on 22 Aug 2012 at 8:59

[GoogleCodeExporter]

Android 2.3.4 does not allow to use large heap. Upgrade your device to android 
4.0.3 or 4.1

Original comment by Andrei.K...@gmail.com on 22 Aug 2012 at 11:03

[GoogleCodeExporter]

That's really not an option. However, if your software reliably and repeatably 
crashes in android 2.3.4 and earlier, you need to modify your manifest to 
exclude those targets. Otherwise folks will keep downloading it from the Play 
Store and leave negative feedback. The cleaner alternative would be to clean up 
memory management to support devices with smaller heap, wouldn't it?

That said, the app also crashes on Google Nexus 7, which runs Jelly Bean, with 
very similar logs.

Original comment by ugra...@323go.com on 22 Aug 2012 at 11:07

[GoogleCodeExporter]

"However, if your software reliably and repeatably crashes in android 2.3.4 and 
earlier, you need to modify your manifest to exclude those targets."

I beg to differ. Crashing could due to the particular hw or sw configuration 
you are using. I am using Android 2.3.1 and I don't have that problem at all. 
I would mind if ebookdroid was pulled from the market for my device.

My performance setting:
pages in memory 0
bitmap reusing yes
bitmap allocation hack NO
native graphics yes

Original comment by peltio on 26 Aug 2012 at 9:55

[GoogleCodeExporter]

@peltio - The developer has already pinpointed the problem to Android 2.3.4 
when he said "Android 2.3.4 does not allow to use large heap. Upgrade your 
device to android 4.0.3 or 4.1".

If that were true, then he would indeed need to exclude those target -- but I 
don't think the reason he gave is accurate, thus my statement. I have also 
further identified that the app crashes on Nexus 7, which runs Android 4.1.

The real question remains as to what we can do to help the developer 
trouble-shoot the issue and hopefully fix it. eBookDroid could be a great app 
and reach millions of users on Kindle Fire if only it worked. 

Original comment by ugra...@323go.com on 30 Aug 2012 at 2:15

[GoogleCodeExporter]

Main problem in debugging such issues is that we do not have hardware to 
reproduce and test. Emulator != real device with the same OS version.

Original comment by Andrei.K...@gmail.com on 25 Oct 2012 at 7:57

[GoogleCodeExporter]

All rendering and memory allocation code were rewritten. Bug is not actual.

Original comment by Andrei.K...@gmail.com on 20 Dec 2012 at 9:35

• Changed state: Done