Map view crashes if zoomed out too far

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I downloaded the map of germany and the wifi catalog.
2. Enable both 
3. Go to the map view of the client
4. click on the zoom out button about 10 times

What is the expected output? What do you see instead?
After the 10 or 11th zoom out the map is no longer responding and after a few 
seconds a crash message is shown and the client exits.
It now will keep crashing when the app is started again and you switch to the 
map view.
I could solve this by downloading and enabling a very small country 
(luxembourg). This seens to reset the invalid zoom level so it then enabled the 
german map to work again.

What version of the product are you using? On what operating system?
This happens for any of the apks in git  on a Samsung Galaxy Y (GT-S5360) 
running Android 2.3.6

Please provide any additional information below.
-

Original issue reported on code.google.com by loshaw...@gmail.com on 3 Sep 2013 at 11:50

• Blocking: #17

[GoogleCodeExporter]

At the moment there is no mechanism to restrict number of overlay objects. 
Instead all objects within visible bounding box are displayed. So I assume the 
device simply runs out of memory and crashes.

Possible solutions:
1) restrict number of objects displayed
2) display objects only up to a certain zoom level

Personally I prefer the latter, as there is only a "point cloud" on high zoom 
levels anyway.

Original comment by wish7code on 3 Sep 2013 at 7:23

• Changed state: Accepted

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

OK, now I can reproduce this bug. After looking at the logcat it seems to be an 
bug in the mapsforge component 
(http://code.google.com/p/mapsforge/issues/detail?id=410)

Original comment by wish7code on 3 Sep 2013 at 9:13

Attachments:

• logcat.txt

[GoogleCodeExporter]

Original comment by wish7code on 5 Sep 2013 at 2:19

• Now blocking: #17

[GoogleCodeExporter]

In a nightly code-rush I updated mapsforge from 0.3.1 to 0.4.0. 
(grab e.g. r26f3429381ca or the unstable binaries at 
https://googledrive.com/host/0B97gHr4MqjHpM2h0QVR5SWJOcGs/), so this bug is 
gone..

So far there'll be no update at F-Droid, as we have to test everything properly 
before releasing. So if you like the F-Droid automatic update mechanism, just 
wait for a couple of more days for a stable release instead of installing above 
binary.
(reference: 
https://f-droid.org/repository/browse/?fdfilter=openbmap&fdid=org.openbmap). 

Original comment by wish7code on 16 Sep 2013 at 11:54

• Changed state: Fixed