Fix: track editor suddenly accelerates touch and moves track

[TobyHFerguson]

While editing a new way and then after attaching it to an established way a node on the established way will suddenly get moved very quickly, and any attempt to move it back shows it the movement being highly exaggerated, making the drag motion impossible to control. In particular no edit record is kept so 'undo' doesn't work.

I’ve attached a screenshot of the end result - the 'airborne' trail has jumped all over the place.

[TobyHFerguson]

I checked the changes against the server version and this is all a rendering problem. No actual changes for this mess were made.

[bryceco]

Thanks for the report. You should definitely clear the OSM cache before proceeding, that should fix the underlying issue.

[TobyHFerguson]

Thanks. Will do. Hopefully you can figure this out and fix it. In your Copious Spare Time! TobyOn Sep 20, 2026, at 23:32, bryceco ***@***.***> wrote:bryceco left a comment (bryceco/GoMap#1008) Thanks for the report. You should definitely clear the OSM cache before proceeding, that should fix the underlying issue. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[tazz4843]

I have had this same issue twice but I have not found a reliable reproduction. As with above, looking in the "pending changes" dialog, no edits show up for the dragged node so nothing gets modified on the server. However in practice Go Map ends up becoming unusable presumably because it's rendering such a long way (I had a node shoot 125km away) so I export and upload via JOSM.

If there's anything that can help if I do encounter this issue again let me know :)

[bryceco]

Can you confirm the app version?

[tazz4843]

The version in the osmChange.osc file for the first time this happened is 5.6.9. I do not remember what it was for the second time this happened, however I think it predated 6.0.0's release. I haven't had this yet with 6.0.0 (at least that I know for sure) so perhaps it is fixed.

[bryceco]

I fixed a related bug in 6.0.0 that Claude was convinced could cause the behavior you describe as a side effect. That bug was a data corruption caused by a race condition while downloading data, so not something easy to reproduce. I think there is a good chance you won't see it in 6.0.0.

[TobyHFerguson]

I was using 5.6.9 when its happened. It’s nothing to do with map downloading. I am using offline maps and it’s happened when I add a way very close (a few pixels) from another existing way, under very zoomed in conditions. My workaround was to not get ‘too close’ and to leave a fixme to connect later. TobyOn Oct 2, 2026, at 15:20, bryceco ***@***.***> wrote:bryceco left a comment (bryceco/GoMap#1008) I fixed a related bug in 6.0.0 that Claude was convinced could cause the behavior you describe as a side effect. That bug was a data corruption caused by a race condition while downloading data, so not something easy to reproduce. I think there is a good chance you won't see it in 6.0.0. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[bryceco]

nothing to do with map downloading

I should clarify: the data corruption happens during download, especially if you're scrolling around downloading a large area. You'll see the effect later when you touch one of those objects that got corrupted.

What you describe being very zoomed in and close might be the same bug or something else.