Large images cause OutOfMemory issues

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Create a directory in 'my documents' with more than 10 epub files 
   with their respective JPG covers.
2. Bring up Trook and browse to the directory.
3. The very first entry into the directory will cause Trook to exit
   after a couple of covers have been scanned.
4. Subsequent entries into the directory will be successful.
5. Enter into a different large directory and the problem will start
   back at (2).

What version of the product are you using? On what operating system?

> Trook rev-53 , however, it also happened with rev-38 
> from the 1.2 softroot

I don't know if this is a problem with Trook, or with the underlying
directory scan mechanism or what. The epub books are personal books,
no DRM and in the order of about 70 pages in size.

Is there anything I can do to better help diagnose this issue?

Thanks.

Original issue reported on code.google.com by oostr...@gmail.com on 20 Feb 2010 at 1:39

[GoogleCodeExporter]

Could you examine the output of adb logcat and send any exceptions you see?

Original comment by kbsriram on 21 Feb 2010 at 2:26

[GoogleCodeExporter]

Ah.  Good debugging tool.  It is a memory allocation exception.  I can make the
problem happen by just hitting refresh in the directory.  In the directory I 
have 10
epubs (roughly 500K in size, each) with their respective cover image jpgs. Each 
cover
image is 590x750 pixels and they are roughly 85K in size, each).

See attached file for the log...

( I have about 350+ files, usually grouped in a directory of 50 or 100 pocket 
books
per episode.  I would like to maintain a directory structure, hence the use of 
Trook.
Why Barnes and Noble allows you to expand the memory storage to 16G of space and
still throws *all* books in one flat representation no one knows...)

Original comment by oostr...@gmail.com on 21 Feb 2010 at 7:29

Attachments:

• Trookv53-02212010.log

[GoogleCodeExporter]

Ah, ok.

Yes, it's the cover images, not the epubs that are causing the problem [trook 
doesn't
load the epub itself.] For the moment, if you're able to replace them with 
smaller
sized jpegs, you'll be able to work around the issue, and also likely load your
directories quicker.

I'll refile this as an issue to use a less clumsy way of loading the images, or 
at
least fall back to just showing the titles should memory start getting scarce.

Original comment by kbsriram on 22 Feb 2010 at 4:23

• Changed title: Large images cause OutOfMemory issues
• Changed state: Accepted

[GoogleCodeExporter]

Thanks....

Original comment by oostr...@gmail.com on 23 Feb 2010 at 1:52