Map becomes stuck when zooming to place search result #2391

Closed
opened 2025-04-26 14:18:52 +00:00 by danieldegroot2 · 2 comments

User searches for some place, clicks on result, map zooms to place. User starts dragging (zooming/loading POIs has not quite finished, so I suppose it is the users fault also)
Map becomes stuck; can not zoom or move map.

Returns browser console errors

service-worker.js:181 CRASH IN SW: InvalidStateError: Failed to execute 'respondWith' on 'FetchEvent': The event handler is already finished.
    at service-worker.js:158:49
    at step (service-worker.js:32:23)
    at Object.next (service-worker.js:13:53)
    at fulfilled (service-worker.js:4:58)
(anonymous)	@	service-worker.js:181
step	@	service-worker.js:32
(anonymous)	@	service-worker.js:13
rejected	@	service-worker.js:5

2
service-worker.js:182 Uncaught (in promise) InvalidStateError: Failed to execute 'respondWith' on 'FetchEvent': The event handler is already finished.
    at service-worker.js:182:44
    at step (service-worker.js:32:23)
    at Object.throw (service-worker.js:13:53)
    at rejected (service-worker.js:5:65)
(anonymous)	@	service-worker.js:182
step	@	service-worker.js:32
(anonymous)	@	service-worker.js:13
rejected	@	service-worker.js:5

Can not effectively reproduce.

MapComplete 0.51.1
Chrome 135.0.7049.115 on Windows 10

User searches for some place, clicks on result, map zooms to place. User starts dragging (zooming/loading POIs has not quite finished, so I suppose it is the users fault also) Map becomes stuck; can not zoom or move map. Returns browser console errors ``` service-worker.js:181 CRASH IN SW: InvalidStateError: Failed to execute 'respondWith' on 'FetchEvent': The event handler is already finished. at service-worker.js:158:49 at step (service-worker.js:32:23) at Object.next (service-worker.js:13:53) at fulfilled (service-worker.js:4:58) (anonymous) @ service-worker.js:181 step @ service-worker.js:32 (anonymous) @ service-worker.js:13 rejected @ service-worker.js:5 2 service-worker.js:182 Uncaught (in promise) InvalidStateError: Failed to execute 'respondWith' on 'FetchEvent': The event handler is already finished. at service-worker.js:182:44 at step (service-worker.js:32:23) at Object.throw (service-worker.js:13:53) at rejected (service-worker.js:5:65) (anonymous) @ service-worker.js:182 step @ service-worker.js:32 (anonymous) @ service-worker.js:13 rejected @ service-worker.js:5 ``` Can not effectively reproduce. MapComplete 0.51.1 Chrome 135.0.7049.115 on Windows 10
Owner

Yeah, I've had it happen once too, but couldn't reproduce either...

Yeah, I've had it happen once too, but couldn't reproduce either...
Owner

Upon closer inspection: this is indeed a bug in the current production version, where I can reliably reproduce it. I've already fixed it in the dev version though, a few days before you opened this bug. I will thus close this bug, as it is already fixed, but not yet deployed.

Upon closer inspection: this is indeed a bug in the current production version, where I can reliably reproduce it. I've already fixed it in the dev version though, a few days before you opened this bug. I will thus close this bug, as it is already fixed, but not yet deployed.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
MapComplete/MapComplete#2391
No description provided.