OsmAnd crashing since latest (monthly) map update

[Matt Vokes]

Hi.  Since the latest monthly map update for England dated 1.7.2016 I'm seeing "OsmAnd+ has stopped working" error message every few minutes, sometimes every few seconds, sometimes moving a distance of under 10m before crashing.  What I have tried:

1. Re-download the map
2. Clear app cache & data then re-download the map
3. Factory reset the phone & started again from scratch
4. Testing on a different phone running 5.1.1 Lollipop (6.0.1 Marshamallow on the other device)
5. Setting a destination on both phones, commence navigation but remain stationary in the house, leaving the screen on.  The app remained stable on both phones during the test duration, approx 30 minutes

Nothing else has changed & app was fine before the map update released about 3 or 4 days ago.  Has anything changed in the map rendering to cause this?  Is anyone else seeing this issue?  Both test devices are Note 4, still a capable device.

Thanks all.

[nickjoh...@gmail.com]

Hi,

It might help if you can install adb and use adb logcat to see what OsmAnd is doing just before it crashes, and whether it's the same problem every time.

Nick

[Harry van der Wolf]

Please remove the map in Osmand or with a file manager and download again. It might be some error in the map while downloading.

If that doesn't help please specify start and destination in your route so that others can try to reproduce your crash.

Harry

--
You received this message because you are subscribed to the Google Groups "Osmand" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Matt Vokes]

Hi unfortunately it's not simply a case of re downloading the maps.  I'm seeing the issue on 2 x Note 4, both have had fresh install of OsmAnd+ & clean download of maps.  One of them I even factory reset the phone.  I also tested on an old Galaxy Tab 3 on 4.4.2 KitKat on which OsmAnd+ also crashed twice.

I ran a simultaneous test on all 3 devices this morning going to the same destination.  All 3 crashed, Note 4 Lollipop within a 100 metres of setting off, Tab 3 froze shortly after, Note 4 Marshmallow lasted maybe 2 minutes before crashing.  Tab 3 is still completely frozen, I cannot yet run adb on it.  I'm not entirely sure what I'm looking at but here are the logs from Note 4 lollipop:

I/ServiceManager(  398): Waiting for service AtCmdFwd...

F/libc    ( 7295): Fatal signal 6 (SIGABRT), code -6 in tid 7314 (Loader map obje)

I/DEBUG   (  335): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

I/DEBUG   (  335): Build fingerprint: 'samsung/trltexx/trlte:5.1.1/LMY47X/N910FXXU1COJ3:user/release-keys'

I/DEBUG   (  335): Revision: '12'

I/DEBUG   (  335): ABI: 'arm'

I/DEBUG   (  335): pid: 7295, tid: 7314, name: Loader map obje  >>> net.osmand.plus <<<

I/DEBUG   (  335): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------

I/DEBUG   (  335):     r0 00000000  r1 00001c92  r2 00000006  r3 00000000

I/DEBUG   (  335):     r4 aef11db8  r5 00000006  r6 0000000c  r7 0000010c

I/DEBUG   (  335):     r8 000857f3  r9 9182bf98  sl 3e31bea0  fp aef1143c

I/DEBUG   (  335):     ip 00001c92  sp aef113d0  lr b6d5d71d  pc b6d81344  cpsr 600f0010

I/DEBUG   (  335): 

I/DEBUG   (  335): backtrace:

I/DEBUG   (  335):     #00 pc 00038344  /system/lib/libc.so (tgkill+12)

I/DEBUG   (  335):     #01 pc 00014719  /system/lib/libc.so (pthread_kill+52)

I/DEBUG   (  335):     #02 pc 00015337  /system/lib/libc.so (raise+10)

I/DEBUG   (  335):     #03 pc 00011bd1  /system/lib/libc.so (__libc_android_abort+36)

I/DEBUG   (  335):     #04 pc 00010044  /system/lib/libc.so (abort+4)

I/DEBUG   (  335):     #05 pc 000a218c  /data/app/net.osmand.plus-1/lib/arm/libgnustl_shared.so (__gnu_cxx::__verbose_terminate_handler()+276)

I/DEBUG   (  335):     #06 pc 0009ff78  /data/app/net.osmand.plus-1/lib/arm/libgnustl_shared.so (__cxxabiv1::__terminate(void (*)())+8)

I/DEBUG   (  335):     #07 pc 0009ffbc  /data/app/net.osmand.plus-1/lib/arm/libgnustl_shared.so (std::terminate()+20)

I/DEBUG   (  335):     #08 pc 000a0144  /data/app/net.osmand.plus-1/lib/arm/libgnustl_shared.so (__cxa_throw+148)

I/DEBUG   (  335):     #09 pc 000a0af0  /data/app/net.osmand.plus-1/lib/arm/libgnustl_shared.so (operator new(unsigned int)+132)

I/DEBUG   (  335):     #10 pc 000c8889  /data/app/net.osmand.plus-1/lib/arm/libosmand.so (std::vector<std::pair<int, int>, std::allocator<std::pair<int, int> > >::operator=(std::vector<std::pair<int, int>, std::allocator<std::pair<int, int> > > const&)+38)

I/DEBUG   (  335):     #11 pc 000d8fdf  /data/app/net.osmand.plus-1/lib/arm/libosmand.so (readMapDataObject(google::protobuf::io::CodedInputStream*, MapTreeBounds*, SearchQuery*, MapIndex*, unsigned long long)+954)

I/DEBUG   (  335):     #12 pc 000d955d  /data/app/net.osmand.plus-1/lib/arm/libosmand.so (readMapDataBlocks(google::protobuf::io::CodedInputStream*, SearchQuery*, MapTreeBounds*, MapIndex*)+220)

I/DEBUG   (  335):     #13 pc 000d96f9  /data/app/net.osmand.plus-1/lib/arm/libosmand.so (searchMapData(google::protobuf::io::CodedInputStream*, MapRoot*, MapIndex*, SearchQuery*)+240)

I/DEBUG   (  335):     #14 pc 000d98c1  /data/app/net.osmand.plus-1/lib/arm/libosmand.so (readMapObjects(SearchQuery*, BinaryMapFile*)+364)

I/DEBUG   (  335):     #15 pc 000d9983  /data/app/net.osmand.plus-1/lib/arm/libosmand.so (readMapObjectsForRendering(SearchQuery*, std::vector<MapDataObject*, std::allocator<MapDataObject*> >&, std::vector<MapDataObject*, std::allocator<MapDataObject*> >&, std::vector<MapDataObject*, std::allocator<MapDataObject*> >&, std::vector<MapDataObject*, std::allocator<MapDataObject*> >&, int&, bool&, int&)+66)

I/DEBUG   (  335):     #16 pc 000dad19  /data/app/net.osmand.plus-1/lib/arm/libosmand.so (searchObjectsForRendering(SearchQuery*, bool, std::string, int&)+80)

I/DEBUG   (  335):     #17 pc 000f0997  /data/app/net.osmand.plus-1/lib/arm/libosmand.so (Java_net_osmand_NativeLibrary_searchNativeObjectsForRendering+298)

I/DEBUG   (  335):     #18 pc 005d47f1  /data/dalvik-cache/arm/data@app@net.osma...@base.apk@classes.dex

Thanks for looking I hope you can help.  I am going on a trip next week & as ever OsmAnd+ is a crucial part of it!  Is there anywhere I can download a the June 2016 maps please? It was working just fine until the map update

Cheers

[Matt Vokes]

Just to confirm, I am seeing the crash on both full maps & roads only version.  The destination makes no difference, it also crashes on default "browse map" option with no destination set.  I'm thinking possibly some form of issue with the rendering of the map, perhaps memory issue?

If there's no quick fix, if there's anywhere I can grab the June 2016 maps it would be a massive help.  

Cheers, all the best

[Harry van der Wolf]

I also asked you to give us your departure and destination. In that case more people can check if it is an error in the July maps or not.

--

[Matt Vokes]

Hi Harry, as detailed I see crashes on 3 devices on any given destination (using navigation) or just driving round on the default browse map setting with no destination set.  In my testing at home using 2 test devices, OsmAnd+ did not crash however with a destination set when remaining stationary.

If you want specifics, the first route I took after the July map update when the crashes started was from departure Lat 52.60085 Lon -1.68302 to destination Lat 52.47364 Lon -2.10563

Thanks, I hope that helps, fingers crossed for a solution

[Mike Pinsent]

On Sunday, 17 July 2016 20:11:29 UTC+1, Mike Pinsent wrote:

Just found this thread. 

I am having the exact same problem.

 

LG G3 Tried various previous version, different maps but all of them autoclose the app at random times if movement of the map or navigation happens.  Some roads disappear at mid zoom levels.  Found that the navigation does not crash if running in the background; I had google downloaded map running navigation and Osmand+ navigating in the background - no crash. Is it possible to get a June map - it will immediately identify if the problem is with the July map?

 

Please please help - Google turns the phone into a heater and uses expensive data,

Sygic+ is totally frustrating (e.g. routed a 10 mile detour down minor roads when the obvious route was 100m the other way.

[Dave Booth]

Just downloaded latest England maps & whilst simply browsing the map (no navigation), I'm also getting OsmAnd closing and phone home screen refreshes. Memory issue?
I'll look further into it if needed

[Dave Booth]

I meant OsmAnd crashes, not just closes.

[Mike Pinsent]

I have explored the memory being responsible - ram never exceeds 80% and CPU well within normal range. It is rendering that seems implicated, it is noticeably slower rendering, why, I have no idea. 

[Harry van der Wolf]

There is indeed something wrong with the English map.

The full map is 776MB compressed  and uncompressed 1.2GB, and the roads_only map is 759.6MB (compressed). That is ridiculous.

I recreated the England map and it crashes at 1.2GB during the poi creation phase.

I tried to create the map from the regional submaps. 

I think you should file a bug ticket. I don't know whether it is OsmAndMapCreator, one of the submaps, or some POI corruption.

issues link: https://github.com/osmandapp/Osmand/issues

Harry

--

[Harry van der Wolf]

Sorry, I guess my answer is way too short. 

Even though the map creation crashes it leaves an seemingly correct obf behind. When checking it with inspector no errors are displayed.

However, when you move "over" the map while navigating or just driving I think it will try to display POIs. Because that part is internally corrupt or at least incomplete, I think OsmAnd crashes.

Harry

[Mike Pinsent]

I did wonder at the file sizes - didn't seem right.

I am having the same problems.

 

LG G3 Tried various previous version, different maps but all of them autoclose/crash the app at random times on movement of the map or navigation. Some roads disappear at mid zoom levels.  

 

Found that the navigation does not crash if running in the background; I had a google downloaded map running navigation and Osmand+ navigating in the background - no crash. Is it possible to get a June map - it will immediately identify if the problem is with the July map?

 

Please please help - Google turns the phone into a heater and uses expensive data,

Sygic+ is totally frustrating (e.g. routed a 10 mile detour down minor roads when the obvious route was 100meters the other way.ic o

I tried the republic of Ireland map - same issues.

[Mike Pinsent]

[Harry van der Wolf]

Does it also crash in simulation mode?

[Matt Vokes]

Thanks to everyone for your input, hopefully we can get this resolved.  To answer Harry, yes it also crashes in simulation in the debug plugin.  I've posted in the issues thread over at GitHub 

https://github.com/osmandapp/Osmand/issues/2831

I was hoping the issue related to some corruption somewhere in the England map only so it's worrying that it's also been spotted in the Republic of Ireland map too.  I've downloaded region maps for most of England & will test locally tomorrow.

Anyone have or know a way to download the June maps?  I usually have previous version of the map on a device somewhere "just in case" but this time I needed a micro SD for something else & formatted it.

[Dave Booth]

Matt, I have the June / England map on my tablet still (didn't update it while away on holiday).
If you can suggest a way of sending it to you - or rather, a link from DropBox, or Google-Drive, then you're welcome to it :-)

[Matt Vokes]

Dave you are a gent, thanks very much. I've sent you an email. Really appreciate your help, cheers.

In the meantime I can confirm that the crash still occurs when using regional maps for England (tested on West Midlands/East Midlands)

Thanks again

[Mike Pinsent]

Matt, does the June maps solve the issue?
So glad this issue is being taken seriously.
Thanks

--
You received this message because you are subscribed to a topic in the Google Groups "Osmand" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/osmand/QCsaE48ITRU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to osmand+un...@googlegroups.com.

[Matt Vokes]

I can't see why not Mike, the app would still be working perfectly if we hadn't updated the map - nothing else has changed.  I've sent a link to a shared folder to Dave, fingers crossed he'll have the opportunity to upload the June map to it.  Are you after them yourself?  Let me know & I'll get them to you once I have them.

Cheers

[Harry van der Wolf]

You can always share via Mega: https://mega.nz/

Harry

--

You received this message because you are subscribed to the Google Groups "Osmand" group.

To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.

[Dave Booth]

Thanks Harry,
I'm just trying the Google Drive upload now. If any issues, I'll get it done via Mega.

[Dave Booth]

OK Matt,
It's in your shared G-Drive folder.
As backup, I'll use Mega (forgot I'd subscribed to that already).
Let me know if there are any problems.

[Dave Booth]

Here's a Mega upload, link (hopefully) for the GB-England OBF map......

https://mega.nz/#!1wAiWCKT

Decryption key...even though i said ''without key''......

!9O52O6sLclJ20AWFSDUoPcQvX2jHLnAuzorm9cfgJIE

[Mike Pinsent]

I did initially think it was my phone as osmand had been so stable and the maps improving all the time. If the June maps are ok, i would be happy with them for months. My Tomtom ones are 10yrs old and display me going through fields where new roads are used! If they are ok, i would love the link, do you think it would be ok for me to download and save the file to share with anyone else they has the problem.

Great to have able people on the forum.
Mike

[matt...@googlemail.com]

Many thanks Dave Booth!

I have downloaded the June file and can confirm it stops the crashing for me.

The app was being killed for me after scrolling around a little.  Particularly when viewing the Canary Wharf area.  I noticed nothing strange being reported by OsmAnd in the adb logs, but there were low memory warnings.  OsmAnd was using upwards of 500mb of RAM.

[Matt Vokes]

Thanks Dave, this has solved the crashing issue, proves 100% there is an issue with the July maps.  One thing to mention is I tried downloading on phone then moving into OsmAnd files folder using a file explorer & kept getting "obf not supported" error.  Downloading to laptop & moving the map file over from there worked absolutely fine so try that if you have any issues.

I hear you Mike but I like the most recent maps ...several times abroad & in the UK I've found myself in need of somewhere to eat or hunting for a toilet etc & the data in OsmAnd (OpenStreetMap) has saved the day.  On the odd occasion I get a spare hour here or there I've become pretty active updating my local part of the city in case anyone finds themselves in a similar situation.

Lets hope they fix this, I suspect we'll probably have to wait for the August update to find out.

[Harry van der Wolf]

If it's only for car navigation, the addresses and POIs you could also try the roads_only map of England of July and switch to the full map back in August (if it's solved).

Just note that you should not have 2 maps active of the same region. OsmAnd will see the roads in both maps and route calculation will be twice as long.

However, when it's really murphy's law striking here the roads_only map might be damaged as well :)

Harry

--

You received this message because you are subscribed to the Google Groups "Osmand" group.

To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.

[Matt Vokes]

Hi Harry.  The app also crashes when using the roads only map for England, see my post of a few days ago.  When testing I am always sure to use only one version of the map to avoid potential conflicts.

PS  I never had chance to say thanks for your postcodes POI file, a great help especially considering how clunky the general address search is in OsmAnd (the search facility sometimes lets down an otherwise fantastic app, especially for new users less inclined to fight through it!).  Cheers Harry

[Dave Booth]

Glad that June file sorted it Matt...and thanks for the tip for moving it over to the OsmAnd root folder. I'll do the same on my phone.
Cheers

[Mike Pinsent]

Thanks to all - I had fun downloading from Mega - said it couldn't download, but it did to my phone. I deleted the July map and placed the June file in its place. Am I right that to stop Osmand+ reinstalling the July file, in Android, I just turn off the notification for Osmand.  I will keep June as a backup in case August has a problem. 

Does the silence of all the other thousands who run Osmand indicate that the July map was Ok for them?

Can we keep this thread going for a couple of months just to be sure and possible hear what actually was causing the problem. As mentioned above it is strange that the July update was so much smaller than the June one.

Thumbs up to you all

On 20 July 2016 at 00:39, Dave Booth <dr.bo...@gmail.com> wrote:

Glad that June file sorted it Matt...and thanks for the tip for moving it over to the OsmAnd root folder. I'll do the same on my phone.
Cheers

[Graeme]

Hi Dave,
I have a Moto G3 and I'm having exactly the same problem. I'm on holiday in Cumbria right now and could do with the fix!

I've tried using your upload link that you posted, but no joy although I've opened a Mega account.

Any ideas how to fix this. Thanks for your help.
Graham

[Matt Vokes]

Private message sent

[Dave Booth]

Hi Graeme,
Just seen Matt sent a private message...hopefully with a link to his location of the file?
I just checked my link and it still works....but your browser needs to be changed to "desktop" mode. Initially when I checked it refused, because my web browser on this tablet was still in "mobile" mode. Changed to desktop, and it worked.
Anyway, hopefully you've got it by now?

[Dave Booth]

Mike, on my phone I have to manually update the maps, so if you don't do anything, that should be fine. .....as far as I'm aware :-\

[Dave Booth]

Not sure if this helps, but I get an immediate crash if doing the following ...
- display a set of certain POI's on the map (I used Post Codes from Harry).
- click on a POI (still ok)
- open menu & select "show details"...
- crash!.
- crashes on just hitting menu button sometimes.
Tried other POI built in...and they seem ok. Not crashing. Every time I click on a post code & try to view menu, it crashes.

Anyone with UK map / July & Harry's Post codes able to reproduce this?

[Harry van der Wolf]

I will have a look at "normal" POIs in the OsmAnd OBF files and my Postcode POI files.

Can you also reproduce this with the June maps? Or do they function correctly?

Anyway: my POIs are "bare" POIs and don't contain any additional info (at least not in the current and previous versions)

Harry

--

You received this message because you are subscribed to the Google Groups "Osmand" group.

To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.

[Dave Booth]

Darn it.....didn't expect any issues with June map, but unfortunately ...the crash occurs doing the same "click on menu" action on the June map, so it's not relevant.
I'd not done this before, as.., as you say, there's no additional info I'd expect to find.
That's a red getting then, sorry.
:'(

[Dave Booth]

"Red herring", rather.

[Harry van der Wolf]

The crashing of the July maps has nothing to do with my Postcode POI file.

The crashing with my POI Postcode file has a completely different cause and will occur will all maps to "some" months back.

I use the POI tag "user_defined_other: postcode".

When sniffing through other OBF files and then in OsmAnd's code on github.com/osmandapp I found the issue.

That "user_defined_other" tag is since "some"(?) months no longer supported. That makes that OsmAnd crashes as it can't find out which additional info belongs to that POI tag.

I have to look at what's now supported and recreate the POI map again. 

The address maps don't suffer from this POI issue.

Harry

2016-07-21 18:36 GMT+02:00 Dave Booth <dr.bo...@gmail.com>:

"Red herring", rather.

[Dave Booth]

Thanks Harry. I agree of course...the crashing with the post codes isn't relevant to the July map issues after all....and wouldn't under normal circumstances have been noticed if I hasn't been rooting around trying to see what initiated a crash.

Hope you don't have to spend too much time on your post codes file. It's certainly indispensable as-is :-)

[Harry van der Wolf]

See for a status update on the POI file the orginal mail thread "New July 2016 UK-postcode files: again both as address and as POI file"  or via the Google Mail groups site:  https://groups.google.com/forum/#!topic/osmand/ZIDFWM50OW4

Harry

[Dave Booth]

Many thanks Harry. Downloaded & replaced older file.

[Dave Booth]

Hi Harry,
No fresh news on https://github.com/osmandapp/Osmand/issues/2831 ?
I'd posted the Cyprus map glitch on there - before being ticked off for mixing issues :-\   as I thought it pointed to a "map creation" issue for the July releases, rather than OsmAnd software problem. Seeing as Matt noted an instant fix when he'd replaced his faulty July map with the older (working) June GB-England map, doesn't these problems point suspiciously at that?
My June Cyprus map has no rendering issues on close-zoom. July Cyprus has errors, as I'd posted on github.
Does xmd5a2 not agree?
Thanks.
Dave.

[Harry van der Wolf]

Hi Dave,

I know how to use the tools and have a relative good insight in both the OSM stucture as well as the OsmAnd map structure (at least I think so), but I'm not involved in the java and C++ coding of the OsmAnd map making and map rendering. I can't do anything there. Just like anybody else I'm just an end user and hoping and waiting for a solution.

Harry

[Dave Booth]

:-)
I'll hold on and sit it out with everyone for a fix soon hopefully.

[Mike Pinsent]

Thanks Dave and Harry,

My June England map is working without a flaw. I haven't retried The other UK regions or Rep of Ireland - all of which crashed before.

Just appreciate all the time and interest you guys are putting in.

Mike

On 27 July 2016 at 09:09, Dave Booth <dr.bo...@gmail.com> wrote:

:-)
 I'll hold on and sit it out with everyone for a fix soon hopefully.

--
You received this message because you are subscribed to a topic in the Google Groups "Osmand" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/osmand/QCsaE48ITRU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to osmand+un...@googlegroups.com.

[Harry van der Wolf]

I had the England roads_only map but just downloaded the West-Midlands and East-Midlands and tried Matt's trip (departure Lat 52.60085 Lon -1.68302 to destination Lat 52.47364 Lon -2.10563) in simulation mode.

It works fine for me on 2.3.5 on Samsung S5 mini Android 5.1.1. Everything on default apart from the United_Kindom_postcode POI obf.

Can anyone of you tell me if you use contourlines, one or more POI types displayed, height maps, or other "things"?

Harry

--

You received this message because you are subscribed to the Google Groups "Osmand" group.

To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.

[Dave Booth]

Hi Harry,
I have contour lines as well as hillshade on my maps.

After you asked, I tried scrolling around (the previously suggested) Canary Wharf (which seems feature-rich, and quickly crashes the app). I've not needed to use navigation to cause a crash so far.

I didn't have any POI's on-screen. After ~ 40 seconds, the map became sluggish to scroll around on, and map rendering slowed until black screen & crash within a minute.

I cleared OsmAnd from memory and restarted. After turning off contour lines, I cleared & restarted again, and scrolled around Canary Wharf. Same story - same crash in similar time. Repeated above, turning hillshade off as well, leaving the map as bare as possible. Unfortunately, same crashing, similar time frame.

Hope this helps?
Dave.

[Dave Booth]

Glad the June map is filling in the gap for you till things are sorted.
I'm keeping the newer glitchy July on my phone to test things out for now. June still on my tablet.

[Mike Pinsent]

Hi. I too had contour lines and hill shades. I did try with nothing added and it still crashed. With the June map, the rendering is very fast.

On 27 Jul 2016 19:00, "Dave Booth" <dr.bo...@gmail.com> wrote:

Glad the June map is filling in the gap for you till things are sorted.
I'm keeping the newer glitchy July on my phone to test things out for now. June still on my tablet.

[Harry van der Wolf]

I did a couple of tests. Also browing around Canary Wharf, minutes long.

Once I got a crash but nothing was written to the exception log. Maybe I should also start to look at the logcat.

My phone has 1.5GB memeory. I'm also beginning to think that there is a memory leak. But that would also require more debugging to check and analyse.

I will try the same on my 512MB old phone. If it crashes sooner I will diver deeper in the time consuming debugging. (It's always nice that someone else finds the cause before you start to spend time on it)

Harry 

--

You received this message because you are subscribed to the Google Groups "Osmand" group.

To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.

[Dave Booth]

Using my HTC One M7 phone with the new July map, I just planned a route (with gps on to keep OsmAnd running in the background). Then checked running apps in settings to display RAM usage (OsmAnd was speaking in the background, so still awake). I watched OsmAnd quickly rise to ~800Mb of RAM, before it crashed and caused a restart of a number of other running apps.

Before I'd started OsmAnd there was ~1Gb of free RAM.

I repeated the above same route and procedure on my LG G Pad 8.3 tablet (also has 2Gb RAM) with the June map. OsmAnd used an almost constant 220Mb of RAM and remained stable / useable whilst running in foreground / background. That's in spite of my tablet being much slower item to use in general, compared with my phone.

I'm not sure how much RAM OsmAnd is supposed to use, but 220Mb seems much more realistic than 800Mb.

Dave.

[Harry van der Wolf]

Thank you for testing and adding your findings to the ticket.

To me this even more strengthens my assumption (as that is what it is) that OsmAnd has a huge memory leak somewhere. This could of course be connected to some "anomaly" in the new maps that cause this.

OsmAnd is a huge memory hog anyway and I have already complained about that multiple times in this mailing list. Especially when calculating routes it needs a lot of memory (above 300-400 km > 512MB; above 600km => 1GB memory), but this memory should be released for a great deal after the calculation has finished. 

(Off topic: OsmAnd is also extremely slow when calculating a route. The lack of performance and huge memory usage come due to the heuristic coefficient (=1) and the huge (over optimized) matrix it needs. I did by now many tests with the default heuristic coefficient 1.0 versus 1.2 or 1.3. Apart from the lack of performance and huge memory use with the default 1.0 value, it does even calculate worse routes: longer and slower. I have already complained about this so often that I'm currently "too tired" to start that all again. I use OsmAnd for cycling and hiking/walking, as despite some weaknesses, it is simply the best. I use MapFactor Navigator for car navigation for 2 years now)

Harry

[Dave Booth]

Cheers Harry,
It certainly looks like (in my ignorance) a memory issue with the newer maps initiating the problem. Along with the Cyprus map I'd noticed that had rendering issues at close zoom - appears maybe a glytch in the map generating prog' during July's issue(s).
Hopefully not long to wait now for the August updates and see if anything changes.
Dave.

[Matt Vokes]

Hi all.  Typical install for me consists of World Overview, United Kingdom England, United-Kingdom postcodes poi europe, Wikipedia United Kingdom England, Contour lines United Kingdom England & contour lines plugin.  I do not use the hillshades plugin.

When I first saw the crash I tested on 3 devices, on one of which I did a full factory reset.  Tests were then done with the "bare bones" to try to minimise potential issues

Immediately upon reverting to the June maps for United Kingdom England, OsmAnd has not crashed once.  

I have run my typical set up (as above) with the addition of: July map updates for Norway Hordaland, Norway More og Romsdal, Norway Rogaland, Norway Sogn og Fjordane, countour lines for all of these regions, Wikipedia Norway & Nautical map view plugin.  This setup has not yielded any crashes during the last week - the July map updates for Norway regions do not appear to be affected.

Cheers

[Dave Booth]

First update today for maps I have installed - Cyprus ....and the rendering glitch has (been) corrected.

Fingers crossed for updates to either OsmAnd+ or maps, so GB-England gets fixed.

[Dave Booth]

When checking for map updates for United Kingdom England, (on my tablet with 1June map) there is now no update available beyond this.

Has this been taken offline (July-August updates) for now?

[Harry van der Wolf]

I can see that all regional EN maps are already available for August, as well as the Scotland and Wales map. 

I can also see on the buildserver (http://builder.osmand.net:8080/) that it is still working on generating maps for August. The big full country maps, which are currently generated from the regional maps in a separate job, are therefore the latest to be generated maps. 

Currently (as I'm typing now) it is generating the Dutch regional maps. The lower  "alphabetical" maps are already available, the higher "alphabetical" maps are being worked on and not yet available and neither is the full Netherlands map.

Just guessing here, but I think you have to be a little more patient.

Harry

2016-08-05 14:23 GMT+02:00 Dave Booth <dr.bo...@gmail.com>:

When checking for map updates for United Kingdom England, (on my tablet with 1June map) there is now no update available beyond this.

Has this been taken offline (July-August updates) for now?

--
You received this message because you are subscribed to the Google Groups "Osmand" group.

To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscribe@googlegroups.com.

[Dave Booth]

Thanks for the information and link (saved) Harry.
Patient I'll be ;-)

[Mike Pinsent]

Thanks

On 6 Aug 2016 11:39, "Dave Booth" <dr.bo...@gmail.com> wrote:

Thanks for the information and link (saved) Harry.
Patient I'll be ;-)

--
You received this message because you are subscribed to a topic in the Google Groups "Osmand" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/osmand/QCsaE48ITRU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to osmand+unsubscribe@googlegroups.com.

[Harry van der Wolf]

For those who are really interested in the details.

This file shows the countries/regions for which maps are generated and in which order: https://github.com/osmandapp/OsmAnd-resources/blob/master/countries-info/regions.xml

The current job building the maps is: http://builder.osmand.net:8080/job/Maps_GenerateFullMaps/956/

This is the current console log (in plain text): http://builder.osmand.net:8080/job/Maps_GenerateFullMaps/956/consoleText

Search for "WARNING: ----------- Generate", which is the first line when a new country/regions is being created.

If you save to file and do a "grep "WARNING: ----------- Generate" consoleText.txt" you can see how many it already has created (+500 now), and the full england map is not one of them (and neither is for example the netherlands or italy map).

Harry

--

You received this message because you are subscribed to the Google Groups "Osmand" group.

To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscribe@googlegroups.com.

[AllanR]

One of the posters asked if anyone else is having problems?   Since July I've experienced severe problems with OsmAnd. Prior to then, all was fine. However after loading the latest maps on my S5 phone for going on holiday, OsmAnd crashed every 6 mins on the 125 mile journey. Thinking this might have been caused by a recent Android update, I deleted and re-loaded the app and maps which seemed to help on the return journey. Looking more closely I note that when scrolling a map there's a delay of approx 7 secs before the new section appears. An older tablet takes up to 15 secs to refresh the screen after any map scroll and after a few scrolls the tablet freezes completely.

Here's hoping there's a resolution in sight.

[Dave Booth]

Thank you Harry. Just having a rummage through those links now. Interesting :-)

[Michał Musiałowicz]

Hi,
It seems that August map still causes problems. In my case it is England North East. OsmAnd crashes when browsing map and also during navigation. Also I noticed that calculating route between Edinburgh and Newcastle takes definitely too much time - about two (!) hours.

[Allan Hopkins]

I've had the same Osmand crash with the July England and Wales maps. Osmand continued to crash in simulation mode after updating to the Wales and Scotland 1st August maps. I deleted the England July map and Osmand now works in both simulation and live modes here in Wales. I now await a functioning England map before I venture across the border. 

[Harry van der Wolf]

Even though Victor closed the ticket (without solving it), I still added a comment to https://github.com/osmandapp/Osmand/issues/2831

I hope for a prompt reaction and if not we make a new ticket, referring to this one, until it gets the proper attentions.

This is really a major, showstopping bug. Anyone trying to use the England maps can't do that. Just because someone is that fortunate to still have the old June maps, makes that workaround even more awkward as the development team does not provide a workaround.

Harry

--

[Dave Booth]

Yes Harry, ...a comment of simply "fixed" on github, with no details wasn't particularly helpful. A one liner explanation would have been preferred with a mention that full England map would disappear (temporarily I hope).

[Dave Booth]

Received reply -
https://github.com/osmandapp/Osmand/issues/2831

[Dave Booth]

Apparently a memory leak (no surprise there).
OsmAnd update planned next week.
Waiting patiently again...........

[Harry van der Wolf]

I see I was again too fast with my response. It misses a sentence.

2016-08-06 18:16 GMT+02:00 Harry van der Wolf <hvd...@gmail.com>:

For those who are really interested in the details.

This file shows the countries/regions for which maps are generated and in which order: https://github.com/osmandapp/OsmAnd-resources/blob/master/countries-info/regions.xml

And the regional countries which are joined afterwards have a separate parameter "join_map_files="yes"", like <region name="england" translate="England;entity=relation" inner_download_prefix="gb_england" hillshade="no" poly_extract="west-europe" join_map_files="yes">

[Dave Booth]

Thanks again Harry.

[AllanR]

Since Osmand+ v 2.4.3 update, I've not experienced any crashes (using the Scotland map) which is a relief.  Is this issue now considered resolved for all maps?

[Dave Booth]

Hi AlanR,
Yes, the issue has been resolved. There's OsmAnd 2.4.4 update available also. Apparently the maps were fine, but OsmAnd had developed a leak (memory). Now patched up & nolonger leaking ;-)

[Mike Pinsent]

I will down load and see how it goes. In the meantime i tried Waze and attempted Syngic again. It has improved but far short of Osmand.
Thanks for keeping this thread alive.

On 23 Aug 2016 23:27, "Dave Booth" <dr.bo...@gmail.com> wrote:

Hi AlanR,
Yes, the issue has been resolved. There's OsmAnd 2.4.4 update available also. Apparently the maps were fine, but OsmAnd had developed a leak (memory). Now patched up & nolonger leaking ;-)

[Matt Vokes]

Hi Mike, like Dave I've used latest Play Store release 2.4.6 with August maps for England to navigate several journeys & haven't seen any crashes. They've also fixed the search result display error. Haven't found any show stopping new bugs ...yet lol ☺️

Thanks Victor, the rest of the dev team & everyone in this thread/github helping to resolve the issues. Everyone pulling together shows what a great app OsmAnd is.

Ps I have Waze installed as a back up, it has its uses (traffic) but it's nowhere near as flexible or detailed as OsmAnd & without the fantastic lane guidance in OsmAnd it can be prove difficult to follow at complicated motorway junctions. I can't handle all the social crap - I switch the lot off

[Dave Booth]

Oops.... OsmAnd+ 2.4.6. (I gave the wrong increment number), thanks Matt.
Yeh...great community spirit, cheers. Almost a shame not to have a problem to root about in ;-)

[Mike Pinsent]

Thanks everyone, mine is working without a flaw. I only wish we could link traffic some how.

Full marks everyone and for whoever in OSMAND who fixed the bug.

On 25 August 2016 at 00:36, Dave Booth <dr.bo...@gmail.com> wrote:

Oops.... OsmAnd+ 2.4.6. (I gave the wrong increment number), thanks Matt.
Yeh...great community spirit, cheers. Almost a shame not to have a problem to root about in ;-)

[Harry van der Wolf]

Hi,

Please register an issue instead of creating a new topic.

https://github.com/osmandapp/osmand/issues

Harry

2016-08-27 11:55 GMT+02:00 Allan Hopkins <aho...@gmail.com>:

Great to have OsmAnd functioning again here in Wales. The only bug that I can see from the last update is that the lanes alert display now shows an anti clockwise, rather than clockwise, path around roundabouts. This would make negotiating unfamiliar complex junctions very confusing. I recall seeing this particular bug in an earlier version. How can this bug be brought to the attention of OsmAnd developers e.g. should I post this a a new topic? 

On Friday, 15 July 2016 18:26:41 UTC+1, Matt Vokes wrote:

Hi.  Since the latest monthly map update for England dated 1.7.2016 I'm seeing "OsmAnd+ has stopped working" error message every few minutes, sometimes every few seconds, sometimes moving a distance of under 10m before crashing.  What I have tried:

1. Re-download the map
2. Clear app cache & data then re-download the map
3. Factory reset the phone & started again from scratch
4. Testing on a different phone running 5.1.1 Lollipop (6.0.1 Marshamallow on the other device)
5. Setting a destination on both phones, commence navigation but remain stationary in the house, leaving the screen on.  The app remained stable on both phones during the test duration, approx 30 minutes

Nothing else has changed & app was fine before the map update released about 3 or 4 days ago.  Has anything changed in the map rendering to cause this?  Is anyone else seeing this issue?  Both test devices are Note 4, still a capable device.

Thanks all.

--

You received this message because you are subscribed to the Google Groups "Osmand" group.

To unsubscribe from this group and stop receiving emails from it, send an email to osmand+unsubscribe@googlegroups.com.

[Allan Hopkins]

Hi Harry, It's my error, not a bug. Somehow, the wrong driving region had become selected! Don't know how that happened, but just running a simulation and all now OK. Doh!

To unsubscribe from this group and stop receiving emails from it, send an email to osmand+un...@googlegroups.com.