serious crashing since 2.2.x version

Olaf Skarabis shared this problem 6 years ago
Solved

Hello,


i am using Locus Pro and the optional in App Download from vector maps. This works fine the last 2-3 months. Now since 1-2 days i have the option to download vector maps for a complete country not just for parts like in the past.


Since that time my Locus pro crash very often.


I am not if it is regarding a new Locus pro version or the changes to bigger maps for a complete country. I have this Problem with the German part.


My device is a Sony Xperia Active .


Thanks


Olaf

Comments (50)

photo
0

hi


-> start the app "catlog"


(install free from google play:


https://play.google.com/store/apps/de... )


-> wait 10 seconds and put catlog in the background


-> start locus


-> reproduce your crash / force close / what ever


-> switch to catlog


-> wait 10 seconds


-> save catlogfile from "catlog/saved_logs/..." and send this together


with the crash log from "locus/logs/..." directory to locus(@)asamm.cz


-> dont forget a short description of the error.

photo
0

I have the same problem, also with the german map (downloaded from http://download.mapsforge.org/maps/).


I`ll try to reproduce it and catch the logfile with catlog...

photo
0

Just recreated the issue and catched the logfile with catlog. There was no crash log in locus/logs/.


Sent the catlog logfile to locus(@)asamm.cz.


Hope this helps...

photo
0

hi Mambo,


thanks for logs. It`s full of errors from K9 but from Locus is there only one issue. You just saw dialog that appear after 5 secs of inactivity so you saw "Wait" of "Close" buttons correct? May you describe me what you did that this happen? Best is step by step so I can reproduce it ...

photo
0

Hi Menion,


no, that "Wait/Close" dialog was earlier, that was a problem probably not related to locus.


The problem I mean happened ab about 17:41, I think this:


> "04-25 17:41:31.444 I/ActivityManager(1368): Process menion.android.locus.pro (pid 13961) has died."


is related to it.


To recreate, I choose the german vector map (whole germany downloaded from download.mapsforge.org, after switch to the new version of mapsforge) and start either start a navigation or drive around with auto zoom and maps rotation enabled. After 10-20 minutes, sometimes later, sometimes earlier, locus closes without any error message, just as if I exited it. When I recreated it yesterday, it happened even after a few seconds.


@Olaf Skarabis: is this the same behaviour you observed?


I`ll try again today, also using an online map instead of a vector map.

photo
0

Hi, it looks like that.


normal it would say i have done nothing and it crashed. Actual i am ill so i can not go outdoor for testing, but it happen sometimes 30 seconds after startting locus.


I have used it in the last 2 weeks only for geocaching, nothing else!!


So theire was no other action as looking to the map and finidig a point. And what i have seen after i have done some tests, it also happend if i just switch between big vector maps like france and german - sometimes it crash.


I think i put the smaler map parts again on the device, just for be sure i have a workaround.


Can it be a memory problem - are the cards to big for our devices?


Thanks


Olaf

photo
0

I`m worried this is something worst


two people already wrote me about crashing of locus. Both send me a logs and in all logs was just before crash


menion.android.locus.pro/menion.android.locus.core.MainActivity (server)` ~ Consumer closed input channel or an error occurred. events=0x8


menion.android.locus.pro/menion.android.locus.core.MainActivity (server)` ~ Channel is unrecoverably broken and will be disposed!


but absolutely no clue why this happen. There was no bigger change in last versions except two. New MapsForge library and Sherlock library for Action bar. One of them will probably be guilty, but no matter what I do, cannot find on internet any reason for this, damn ...


mambofive: same in 17.41 in your log, you`re correct

photo
0

what are your devices? Both people that reported me same problem had android 2.3.X

photo
0

For me, it`s a motorola milestone 2 with android 2.3.4

photo
0

fine so it`s some issue in 2.3.x android ...


it`s probably caused by MapsForge or Sherlock library (that`s why I always rather do things by my own), anyway before I`ll try to remove one of them to check source of trouble, let`s try opposite solution


so, check this testing version please, where


- updated one compatibility library from Google itself


- updated MapsForge to current source code


- updated Sherlock also to last version 4.0.2


I really really hope, one of this helps!


http://dl.dropbox.com/u/8015949/Locus...

photo
0

I had the chance yesterday to use the testing version you provided, I used it to navigate ~200km, using the same germany map I used before - no problems!


It seems that one of the three changes you did has fixed the problem.

photo
0

if this is not a joke, then it`s best message last weeks I get, because I started to be really desperate. Really hope more people will confirm this :)

photo
0

I`m sorry to say that this issue still seems to be there in the most current version...


I used Locus a lot the last days, and there are still crashes / forced closes. Sometimes after a few minutes, sometimes after several hours. It seems that when I used the testing version last week, I didn`t use it long enough...


This might be the same problem? BTW, I also noticed that some waypoints or other changes are lost after the crash.


To reproduce, just use Locus with map centered to GPS position, no navigation, no map rotation needed.


The problem occurs with vector maps as well as with online maps - so it`s probably not related to mapsforge-library.


There are no logs in Locus/logs. If I can do anything to help debugging this issue, please tell me.

photo
0

email send to you with testing version, thanks

photo
0

Hi,


I have been using Locus Free with great satisfaction for more than a year, but now I have the same crashing problem as described above. I`m using version 2.3.1. The crash happens every time, right after startup, no user intervention needed. Would you be helped with a catlog?


Regards,


Frits

photo
0

Using the last testing version, no more crashes occured for me.

photo
0

So guys,


even with new version (special private for testing) is Locus crashing, I need some more feedback and testing from You. Seems this is some issue on A2.3.X phones, may you confirm it?


Here is for download current fully working build http://dl.dropbox.com/u/8015949/Locus...


so please:


1) install it. It will install as Locus Free (so backup settings if you use Locus Free) but till 11.4. will work as Locus Pro!


2) start it and check in menu > Locus > About > tab Locus and here should be version 2.3.1.2 and valid till 11.05.2012


3) use it as normal


suggestion: restart phone after install, it may help in some cases


how you can help:


my opinion is that one of features is causing this. That this is not some global problem in Locus. Because in crash logs is only one line with error: "locus has died", it`s absolutely impossible to find source of this issue from logs, unfortunately. So for me, should be best if you could test changing some settings in app and just test if this have influence or not


mainly check:


1. menu > settings > misc > Enable Periodic updates - this is main suspicious so check it please


2. menu > settings > global > Always screen on - this feature work with wake-lock, dangerous feature in Android system so it may cause problems


3. menu > settings > GPS > GPS auto-off - same as "Alyway screen on"


logs may be useful just to check if this is really only error "application menion.android.locus has died" or any other problem with common error that should be simply fixed! Thanks all for your time. This is really my small nightmare mainly because of lack or some error logs and also because on non of my device, no matter what I do and whos settings I import, no problem. Maybe because I`m testing it only on A2.1 and A4.0. Thanks guys!

photo
0

partially good news :). There was also probably problems with old library I used for action bar. So far good, but main problem is probably still there, so check post bellow please

photo
0

Hi,


In installed the 2.3.1.2 version you mention above and it works fine. No more crashes! I`m using an Acer E400 phone with Android 2.1. I followed your instructions above. Then I loaded a 600 MB map onto the SD card and used it without a problem.


Regards,


Frits

photo
0

fine, I did last few days fixing bugs and improving current mainly Action Bar system but I think that some problem will be still there, so in case you`ll find any clue about crashing, it will be welcome

photo
0

I enabled "Periodic updates" some days ago to test gc4locus "LiveMap" feature - maybe this "enabled" the crash problem. In all tests with the free version, this setting was disabled because the test version came with own settings. I`ll try again with the newest testing version and check the influence of this setting...

photo
0

a really hard test is to use eg the netherland vectormap in zoomlevel 10, 9, 8,...


zoom out to 7 and move, freeze my phone. but i think its a known mapforge bug.


maybe you can test this also.

photo
0

Using either the OSM Classic or Mapquest Classic map (online), I can zoom to any level and move around without any problem. Is that what you mean?

photo
0

...Vectormap...

photo
0

@gynta: scrolling in that vectormap at zoomlevel 9 gives me a force close of Locus. Map loading time is huge and restart of Locus gives "sorry, unexpected stop of Locus".


I only could get out of this "loop" by doing a couple of quick zoom-in taps and then maually closing Locus with Back Button (during map loading). Pfoeh.


Sorry, no time for testing now; have to be on the road in an hour for a three days hike with guiding.


Locus version 2.3.1. from googleplay. Android 2.1 on MotoDefy.

photo
0

this is happen also with last test version 2.3.1.2? If so and this is happen really only when you do such CPU intensive operation, may you check logcat? (or send me it) why is this happen?


Anyway it will not be related to crashed we talk about in this topic

photo
0

>Anyway it will not be related to crashed we talk about in this topic


hm


Olaf talking about Vectormap:


"...it also happend if i just switch between big vector maps like france and german - sometimes it crash..."


whatever - the log is in the dropbox..


...oh, i see - you already there :-)

photo
0

Will try to test 2.3.1.2 but not before tuesday, sorry.

photo
0

thanks gynta, log examined. By related I mean fact that when we started this topic, most crashes was really just "locus was killed" and absolutely nothing more. In log from you, is 100 lines of some error messages. Which is not good of course, but from these messages can be found problem.


I`ll try to download also netherland map and check it. I`m worried it will be something you mention, issue in MapsForge. We`ll see.


and Henk, no hurry. I hope in tuesday you`ll be able to test perfectly working version ;)

photo
0

Sorry, I was offline with my DEFY+ and Android 2.3.6 (Geocaching with previous testing version). In the next days I will test the newest version.

photo
0

Did some tests with test version 2.3.1.2.


With "Periodic Updates" activated, it crashes after some minutes. With this option switched off, I didn`t get any crashes.


Also tested the last official Pro version (2.3.1), same behaviour: crashes with "Periodic Updates" switched on, stable with this option switched off.

photo
0

hmm perfect, finally idea where to start. If anyone can confirm this, it should be perfect. In this case, one more question. May you or anyone other also try if this happen also when you have enabled Periodic updates and un-installed all addons that use this feature (only geocaching addons now)? In this case problem will be in Locus (in sending data) itself because there will be not other possibility. In case this will happen only when also add-ons are installed, this will mean that this happen during data receiving

photo
0

Can confirm... Testing version 2.3.1.1 ran very smooth with this option disabled!

photo
0

Guys, thank you!!


I also received before an hour reaction from Ron and Lubomir with exactly same result, so seems problem found. You have no idea how I`m glad for this. So I rewrote whole system and now I`m using service for sending information for add-on. May you check if this works? Don`t expect miracles. I expect that this will be prohibited feature for those with this issue, because I use standart functions, no hack etc. so it have to be system problem


test version: http://dl.dropbox.com/u/8015949/Locus...

photo
0

o.k., just to keep the information complete: I had a short test with that option enabled and gc4locus deinstalled, I still get crashes.

photo
0

perfect, thanks. So it`s definitely very short (around 10 lines) code that cause this crashes. And one part of this has changed in testing version above, so maybe this will help.


If not, I`m worried I have no better idea how to solve it, so you`ll probably loose support for live map in add-ons ...

photo
0

To get things clear... All this trouble was caused by this stupid "geocaching hobby"??? ;)

photo
0

hey it`s not feature just for geocaching. I can imagine many wonderful add-ons that may use this for some periodic updates of stuff on Locus map or just for logging your movement or whatever (information send by "periodic updates" should be added on request)! So don`t blame just geocaching :)

photo
0

This version works fine for me, I didn`t get any crashes so far.

photo
0

Just emailed two logs with the netherlands map problem. Still there with new version.

photo
0

It is definitely a V3 Vector Map thing. I downloaded a new province map (noord-brabant) from here: http://vectormaps4locus.eu/Europe-Net... and now that small map (70 mB) also crashes below zoomlevel 10 and is dead slow when panning the map at say zoomlevel 12

photo
0

thank you for a logs. May you please also try MapsForge own AdvancedMapReader application? http://code.google.com/p/mapsforge/do...


your logs are full of OutOfMemory errors, so it`s really hard to solve it. It may be caused by Locus, but it should be also MapsForge issue. When you`ll run AdvancedMapReader, it should crash less then Locus, because it needs less memory then Locus for own processes.

photo
0

>Menion: "I`ll try to download also netherland map and check it. I`m worried it will be something you mention, issue in MapsForge. We`ll see..."


and your result?

photo
0

Catlog emailed. Adv Map Viewer also crashes.


I restarted my phone (MotoDefy Eclair 2.1 standard)


I use Widgetsoid and it states 162 mB RAM and 878 mB ROM.


I start catlog.


I start Adv Map Viewer and select Netherlands. Slow building of screen, tile by tile.


During I zoom in. Level unknown but km scale says 20 km and next step is 50 km and crash.


So acknowledge "process stopped" and check Widgetsoid.


Still: 161 RAM and 878 ROM. ??


/Offtopic: sorry for late reply, got a wisdom tooth pulled out./

photo
0

The bigger V3 maps Germany (688 mB) and Alps (from the forum, 437 mB) are both fast enough and error free in Advanced Map Viewer and Locus 2.3.1 (present market version).


Zooming down to level 2 even. Ok, take`s a couple of seconds but it works.

photo
0

2.3.1.3 runs very good on my Defy+ (Android 2.3.6).


No crashes during guiding/trackrecording and map with overlay.


I`m very happy!

photo
0

gynta sorry, I didn`t tried maps yet, but from what Henk say, seems to be some issue in MapsForge library, not in Locus.


henk: just info about your RAM information. Total free RAM is totally useless number. Every process have allowed own max limit, usually around 24-32MB and it doesn`t matter how much free memory you have in your system


anyway thanks to Druki any many other people who wrote me email, seems that weird issue is fortunately solved. I`m second day waiting for some stupid Google validation. When this will be done, I`ll immediately release new version

photo
0

>Menion gynta sorry, I didn`t tried maps yet, but from what Henk say, seems to be some issue in MapsForge library, not in Locus.


We know!


The question is: can Locus(you) prevent this crash? Or must we wait...

photo
0

simple answer ... no. This have to be some solvable problem in library. It`s not common error in one place of code so I cannot simply fix it. Suggest to post this issue on their site

photo
0

Ok, nothing changed for me. Advanced MapViewer and Locus 2.3.2 still crash when zooming out below level 10 (50 km) with the Netherlands map 08-May-2012 03:09 version of http://download.mapsforge.org/maps/eu... (as expected)


Bigger maps Germany and Alps (from forum) are doing ok.


Will wait for a new version on download.mapsforge.