Just came on here to see if it was just me but looks like not! Yeah, all my purple lines seem a lot fuzzier - I was out earlier today and noticed the difference a little bit on my phone, but it seems a lot worse and much more noticable on the big computer screen.
Sorry, just to say my life map is pulled from Strava and all the lines are very choppy now and a lot thicker too - makes them look a little blurry, so not sure itās to do with where the data is pulled from
Just realized that the current Lifemap no longer has borders seperating the different States within the United States. I am not sure/do not remember if the different regions within countries were also seperated by a border. Could that be a reason for this problem from the past update?
Also, the GPS lines generated (purple lines) onto the Lifemap are shorter and not completing a street. I have found a few more examples like the one listed in post #7. Those were not there pre-update. My OCD doesnāt allow me to have gaps between intersecting streets during the same run 
.
Oops, I just re-added the state borders ā¦ didnāt mean to drop those. I donāt know how long it will take for the style to reach our browsers.
I suspect that the issues here are somehow related to the issues in the LifeMap crashing on mobile / Jagged lines in LifeMap - #9 by JamesChevalier thread. That issue is much more urgent than this one, so Iāll be coming back to this thread after thatās sorted out. Hopefully at that point the jagged LifeMap lines are also fixed up.
2 Likes
Completely agree! Thanks James
Morning James, sorry, but same here in Sheffield UK - jagged lines and unable to load complete map before it crashes and starts repopulating.
Jim
Thanks for the screenshots - especially because they included the URLs.
I wonder if thereās some bandwidth/latency/networking aspect to this, because Iām not getting the jagged lines:
I can reproduce the page crashing, though. For me, itās isolated to iOS (I donāt have an Android to test with, but Iād assume a similar crashing situation there).
Iāll post more here & in that other thread as I learn moreā¦
The jagged lines started for me recently, too. Not just on new runs, but on past ones.
I am getting the jagged lines, and have for a week or so. I have also noticed things like this. That route (18 months ago) took in Sileby Road, Hayhill, and all the other roads along the way. They are still counted as done in my list of streets, so thatās OK, but it shows me as having done a straight line, missing all the side streets, and Iām sure it never used to. It looks like what happens if I pause and forget to unpause, except that the streets are actually counted.
Hi James, just letting you know that viewing on iPad or iPhone is still the same, but thereās no problem viewing the life map with Firefox on the laptop. Jim
Donāt know if these are any use, but in case they are hereās a couple of screen grabs from me. These are from the computer as canāt really access my life map or any of the city maps from either of my phones at all now, it just crashes straight away.
Looks like it isnāt eally loading properly as Iāve a lot of these randon straight lines on my map now
And this just shows how the jagged lines are showing on my map - browser is Edge, but itās also displaying the same on Firefox/Mozilla
Edited to add Iām in London.
Re-posting this so itās at the bottom of the thread - I just merged two threads together that were effectively discussing the same underlying issue.
Alright, another minor updateā¦
The short version is that I think Iāve spotted something relevant in that the database change I made on Jan 31 seems to have blown away the custom configuration I had set up for it. 
Iāll know more today, as I rebuild the configuration & update the database to use it. Iām guessing this will take me some hours to work on, and then a few minutes of downtime later today.
Iām still quite worried, because I donāt understand how a database configuration change can result in gigabytes of memory use in the browser ā¦ so ā¦ I guess Iām simultaneously hopeful and still sick with anxiety and dread.
More gory details for the Venn diagram of nerds who like watching train wrecksā¦
- Dropping the all the browser-side code back to what existed on Jan 25 didnāt fix/change anything, so it doesnāt seem to be anything particular to the JavaScript running in the browser
- Reindexing relevant indexes didnāt fix/change anything, which is great because those only take a full day to run
- Changing the database instance type back to the original version didnāt fix/change much so it wasnāt just a matter of sizing issues
- āJust waitingā didnāt do anything, which may sound like an odd approach, but I know that some changes in my hosting provider can result in a situation where certain file access slows down for some time after the change
- Reworking the code that builds the LifeMap on each request did improve performance, but didnāt fix/change anything in the browser
Good morning James,
Thanks for all the time youāre putting into this issue, I think itās better, but not solved yet ā¦ā¦
On an iPhone my map will load and, given time, produce the full map which can be drilled into for closer inspection.
However, on the iPad it takes multiple times to load and is fragile - ie. it cannot be made bigger without falling over and starting to reload.
Curiously, when the map has loaded on iPhone and I enlarge it / zoom in, the walked trails are still jagged lines as last week, but given a few seconds they seem to line up in the correct way.
Iāve not checked on the laptop and have to leave the house now.
Good luck!
Jim 
As of this morning, the jagged lines problem appears to be solved.
Interesting William, if I open the link above it still does not always load the map and if I zoom into an area the routes are jagged with a short delay until it corrects itself as previously. Jim
I can confirm the jagged lines have gone away for me as well.
Edit: Iām not sure if itās related, but the date popup when you rollover a route has gone away for me.
Yeah, Iām doing all sorts of debugging ā¦ trying anything to figure this 
out.
The core issue looks like a memory leak, where zooming/panning the map takes more and more memory until the system canāt handle it ā¦ on iOS thatās almost immediately, on a laptop it can take much longer (I actually havenāt pushed it to crash yet, since just seeing GBs of memory use is enough for me).
It doesnāt seem to happen, or it happens way too lightly to notice, for any map with lower numbers of activities.
The jagged lines problem is likely solved / āsolved enoughā ā¦ I do still see them appear, momentarily, here and there ā¦ but nothing worth putting more effort into at this point.
1 Like
On the laptop, yes date rollover gone for me too - didnāt notice that! Itās definitely less jagged than it was on the laptop, though weirdly zoomed out all the lines seem thicker and fuzzier than they were originally. On laptop my map is taking a while to load, a lot longer than before still, but the random straight lines seem to have gone now. As you said James, on the phone iOS itās not useable at all - crashes pretty much immediately.
Thanks for all your work so far trying to fix this - hopefully something works soon!
I was able to get a couple LifeMap pages to load ā¦ Iāve been focusing on @marshall since that page crashed immediately.
Can you all check it out and let me know if thereās still any crashing or jagged lines that donāt get resolved themselves after a couple seconds wait?
Iām unsure how the notifications work for threads, so just in case Iāll mention people who have commentedā¦
// @marshall @templeria @beatlekevin87 @dirkschrama @rcreed @AndyS @dljamet_1999 @4e2c71bc69f7d92608f3 @washley @84978fb94710caedba7a
1 Like
WOOHOO! Looks like it worked! Zoomed way out and then zoomed way in. No crashing. Thank you!!