id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
18835	unexpected full recursive download of children relations makes some edits impossible	verdyp@…	GerdP	"something has changed in JOSM recently, causing it to be unable to resolve edit conflicts for local edits where a parent relation is concerned: the parent relation is now used to perform a FULL recursive download of all its children and subchildrens.
This is a major concern because this happens when trying to resolve an edit conflict: the download will take a considerable time when the parent category is a large and detailed country, causing JOSM trying to download millions of nodes, thousands subrelations, only to complete the dowland status of all of them. Additionallyt, in the 32-bit version you'll rapidly exhaust the memory capacity in the VM and JOSM will hang, error dialogs will not even open all unsaved edits will be lost, the edit conflict will not be solved; all we can do is to kill JOSM with a task manager. When relaunching JOSM, the unsaved edits will be reloaded, but the last submitted data will not be part of the restored data, and some objects that were already saved will be in the wrong state, causing more edit conflicts to resolve.
Now trying to complete only the relations deepest level and checking their update status and resolving these conflicts and submitting them again will not solve the problem for the parent relations.
Even outside the edit conflict editor, now if we have downloaded a relation that has incomplete members for their relation members, if we select that relation and click ""download members"" or ""download incomplete members"", both now perform a recursive download of subrelations and this never ends for large countries.

This is now a severely blocking behavior: we can no longer correctly, esily and speedily fix any edit conflicts, even with the 64-bit version of Java and a large VM (launch parameter: -mx8G). And this takes now several hours when we see the ""downloading"" dialog perform many, many download requests (and finally we get an error from the OSM API because we downloaded too much data in the current session).

Please restore the previous behavior: DO NOT recurse subrelations when downloading members, only recurse nodes of incomplete ways members and at most 1 level of recursion, do not download members referenced of member relations (only download their references: type, and id, possibly their tags like names).

"	defect	closed	normal	20.03	Core		fixed	regression