id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
6252	"Phantom ""unsaved"" layers in 4021, 4032"	T99	team	"Whenever I start JOSM 4021, it reports finding unsaved osm data layers, sometimes hundreds of them.  The error message says:
""Unsaved osm data: JOSM found %d unsaved osm data layers. It looks like JOSM crached last time. Do you like to restore the data?""
However, but I don't recall this version ever crashing on me.  (Once I exited the program and explicitly told it to discard rather than save the data.)
If I discard the ""unsaved data"" and exit JOSM without downloading or opening any data, then the next startup works without this error message. But after any subsequent edits, the next startup shows the message again.
It looks like the autosave feature is leaving some files behind. It should remove all ""unsaved"" data when it's saved or uploaded successfully.
Also, please change the question ""Do you like to restore the data?"" to ""Would you like to restore the data?"".
There is an old, closed bug 5656 which may have been similar."	defect	closed	normal		Core	tested	fixed	autosave, save, unsaved, 4021, 4032