Running out of memory

182 views
Skip to first unread message

alpine14011970

unread,
Nov 8, 2011, 7:00:00 AM11/8/11
to Osmand
I've installed the Japanese vector maps on my tablet, and after some
time browsing the offline maps, I get a message telling me that I have
run out of memory and can not display anymore of the map. How can I
rectify this?

Pavol Zibrita

unread,
Nov 8, 2011, 8:24:44 AM11/8/11
to osm...@googlegroups.com
Hi!

I have encountered also this problem sometimes. Closing the app with X will
help for a while. However, probably you could raise an issue on googlecode
for this. However, it might be problematic to reproduce the problem for us.

Regards,
Pavol

szimszon

unread,
Nov 8, 2011, 3:57:28 PM11/8/11
to osm...@googlegroups.com

Pavol Zibrita

unread,
Nov 9, 2011, 3:48:46 AM11/9/11
to osm...@googlegroups.com
Could be, try to disable native rendering, or the version without native library. If there will be any change.

Regards,
Pavol

Staffan V

unread,
Nov 10, 2011, 5:45:00 AM11/10/11
to Osmand
I have the same problem with my HTC Tattoo, but it's a low end phone
so that might have something to do with it. Off-line routing also
fails due to low memory.
The way I've solved it is to exit OsmAnd and restart it. It also helps
to free up more memory by killing other running apps.

Rem Remmels

unread,
Dec 8, 2011, 8:18:44 AM12/8/11
to Osmand
The problem is still in version 0.7.0 of today.

Once the message is shown the problem persists. Zoom in/out nothing
helps. No further drawing. Even switching to a location with hardly
roads keeps it 'in error'.

The way of rendering has no influence.

It looks that garbage collection does not help here.

Barthwo

unread,
Dec 10, 2011, 1:38:57 PM12/10/11
to osm...@googlegroups.com
The same happened with my version on Adroid 2.3 on a 512 MByte main memory device, Touchlet X7G.

I have configured vector mapping up to level 12. If I go down to 10 and afterwards want to render any map with higher zoom, the memory error occurs.

On my HTC desire with 2.2 and also 512 MByte the error did NOT occur so fast. But after longer times with a moving map it does not work any longer.

Stopping and restarting OSMAND does help and everything starts again.


Reply all
Reply to author
Forward
0 new messages