Jump to content

New Map unbelievable slow and unusable


capsai

Recommended Posts

The new map (https://www.geocaching.com/play/search)  is for me very slow and therefore unusable since a longer period (before, it worked well).

 

When i click on the link in the menu, nothing happened for like 30 seconds before the map opens, even when only 250 caches are shown.

 

It seems, that it works a bit better with Google  Maps instead of the Geocaching Map.

 

The old map (https://www.geocaching.com/map) opens instantly and is fast, but has not the filters from the new map.

 

Also disabling the PGC and GCLH scripts and Tampermonkey won't change anything.

 

The same problem with the new cache owner page.

 

On my smartphone when connected via Wifi, it is the same issue, but connected via mobile network, the new map works instantly.

 

So could this be a specific ISP problem? The rest of the website works for me with an okay-ish speed (its good, but honestly could be faster).

 

Browsers used are Vivaldi and Edge, and Safari on my smartphone.

 

 

  • Upvote 2
Link to comment

I have very similar issues with the map. After logging into geocaching.com and selecting the map -> nothing happens. After around 5 times of retry clicking, the map loads.

 

Some icons are missing. When I click on a cache icon, the browser window gets white, nothing is shown anymore. Currently I cannot use the map function anymore.

Link to comment

Extremely poor response from map. Many times the map will not load and crashes when trying to access satellite view (returns following error) - 

"code": "CSS_CHUNK_LOAD_FAILED",
  "type": "error",
  "request": "https://www.geocaching.com/play/map/public/58.css"
{
  "componentStack": "\nLazy\nSuspense\ndiv\ndiv\nt@https://www.geocaching.com/play/map/public/vendor.655a98c18a2c1e22585b.js:2:758857\nli\nul\ndiv\nMapControls@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:114251\ndiv\nMapControlWrapper@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:113541\ndiv\ndiv\ndiv\nAppComponent@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:98141\nConnect(AppComponent)@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:112496\nSearchProvider@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:86823\nT\nV3Provider@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:395175\nP\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:11705\nE\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:78136\nx\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:16844\nD\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:80282\nA\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:81444\nF\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:18599\nk\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:19109\nN\nMapSettingsProvider@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:85064\n_\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:82140\nI\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:86203\nG\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:83085\nj\n@https://www.geocaching.com/play/map/public/SearchMapDecorators.3fd4c41de38594e6c51c.js:2:29007\nU\nt@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:65937\nSuspense\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:630713\nn@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:549789\nt@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:68053\nt@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:62433\ns@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:355104\no@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:356558\nConnect(o)@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:112496\nf@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:110560\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:544773\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:516789\nb\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:542462\nw\nInitialUrlProvider@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:519085\nx\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:543185\nM\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:139054\nE\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:541673\nA\nUserLookupProvider@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:231418\nC\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:539786\nk\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:510675\nO\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:515241\nS\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:508603\n_\n@https://www.geocaching.com/play/map/public/web-map.3.1.0.9f8b3338f8d535110736.js:2:644771"
}

This problem is recurring and has existed for many months but is never sorted - does an IT team exist at Geocaching?

  • Upvote 2
  • Funny 1
  • Helpful 1
  • Love 1
Link to comment

I have an enormous problem, map-wise. Might belong in a separate post... 

If you go to a CO's list of caches and at the top you click on "Map these caches" it opens a map in a separate tab, great. But if the CO has any archived caches they show up exactly like disabled caches, greyed out. So far, ok. But if you click on one (even just to see what it's called or get the info on left) the clever people at GS made a pop up box "can't find that" and IT TOTALLY FREEZES THE PAGE. Literally you cannot go back or close it by clicking its little 'x'. The ONLY action possible is closing the tab altogether.

 

Bad bug, Groundspeak, very bad.

Oh and p.s. Groundspeak, thanks for disabling the whole archived caches search, you just screwed up all the 'Unknown' (puzzle) caches that need those or link to them. Doh.

Edited by CCFwasG
  • Upvote 1
  • Helpful 2
Link to comment

I am adding to this thread again because MAP ISSUES.

I want to see the geoart near where I am. I know it is there because I can see it on my phone. On the website it showed up briefly and now when I move or 'search this area' again, most of it doesn't show! I have refreshed the page ad nauseum. I have zoomed in and out and clicked search over and over and STILL it won't show the whole thing. It shows most of it sometimes, and only part of it sometimes and literally cannot get it right!

What gives, Groundspeak??? It is totally unworkable. FWIW: Chrome (yeah I know you want us to use other browsers), latest update, PC. 

Link to comment

I am having the same issue with maps. Not every time but in the main when you click on a geocache to open it, or to solve it if it’s a puzzle cache I get the following message pasted below. It’s making the map function unusable 75% of the time. Please fix this. I don’t want to be solving puzzle caches in the app.

 

"code": "CSS_CHUNK_LOAD_FAILED",
  "type": "error",
  "request": "https://www.geocaching.com/play/map/public/235.css"
  • Upvote 1
Link to comment

The problem still persists.

 

Here for example i tried to open the "Events" page and it took 1.5 minutes to load a 12 kB file?

 

What clearly stands out: this poor perfomance only happens with the new pages, new map, cache owner dashboard, event page....

blubb.JPG

Link to comment

So for me the problem has now been solved in a somewhat strange and for me not really comprehensible way:

 

I changed my Pyur (my ISP) tariff to a faster one including new hardware (cable modem and WIFI router) and now the new map, the owner overview page and also the events page opens at normal speed.

 

Strange :o

  • Funny 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...