search

me-azharahmed / osmdroid

Automatically exported from code.google.com/p/osmdroid
0 stars 0 forks source link

Failed to inflate #395

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Use map on ZIP FILE

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

All version of osmdroid (I use latest svn checkout), on all version of Android

Please provide any additional information below.

I attach a stack trace

Original issue reported on code.google.com by zero...@gmail.com on 14 Jan 2013 at 11:16

GoogleCodeExporter commented 8 years ago

Original comment by zero...@gmail.com on 14 Jan 2013 at 11:17

Attachments:

GoogleCodeExporter commented 8 years ago 
Other stack trace

Original comment by zero...@gmail.com on 14 Jan 2013 at 11:31

Attachments:

GoogleCodeExporter commented 8 years ago 
before to crash there is a loop of these messages

Original comment by zero...@gmail.com on 14 Jan 2013 at 11:40

Attachments:

GoogleCodeExporter commented 8 years ago 
What device are you using? The stack trace shows OOME which implies that you're 
using a device with a low amount of memory.

Original comment by neilboyd on 15 Jan 2013 at 6:00

GoogleCodeExporter commented 8 years ago 
I'm using an HTC DESIRE HD (about 500MB of Ram)

Original comment by zero...@gmail.com on 15 Jan 2013 at 9:51

GoogleCodeExporter commented 8 years ago 
I had the same problems. After implementing advice from link 
(https://github.com/glob3mobile/g3m/issues/12) - in AndroidManifest.xml set 
Android application property "largeHeap" to "true" the problem disappeared. I 
know that this solution is temporary and after working some time with big data 
(map tiles data is such a one) the problem may occur again. However for 80-90% 
of situation this is very good solution.

Original comment by shumi.ar...@gmail.com on 23 Apr 2014 at 9:39