id summary reporter owner description type status priority milestone component version resolution keywords cc 11418 Unicode chars >16 bit will crash JOSM Hb--- team "The bike symbol below is the 🚲 unicode character. ==== What steps will reproduce the problem? 1. Delete existing preferences.xml and its backup and start JOSM. 2. Create a new layer and create a new way. 3. Tag the first node with 'keyA=🚲A' 4. Tag the second node with 'keyB=🚲B'. 5. Save the data to a local file like test.osm and close JOSM. 6. Open JOSM again and load the file test.osm. -- Notice that the first nodes value changed to '🚲🚲A'. 7. Save the file test.osm again and close JOSM. -- Notice that in the preferences.xml file the last entry in is now '🚲🚲B'. 8. Open JOSM a third time and load the file test.osm again. -- Notice that the values in both nodes changed to '🚲🚲🚲A' resp. '🚲🚲🚲B' 9. Save the file test.osm a third time and close JOSM. -- Notice that the last entry in is now '🚲🚲🚲🚲🚲B' (Five! bikes). ==== What is the expected result? Using extended Unicode Characters greater 16 bit should not lead to an endlessly growing preference.xml file. ==== What happens instead? JOSM didn't started any more some days after tagging a bike symbol. Error shown in command console was not enough ""Java heap memory"". This was caused by an entry in which was around 300,000 bytes long. That is far over 9000 bike symbols! {{{ Revision: 8338 Repository Root: http://josm.openstreetmap.de/svn Relative URL: ^/trunk Last Changed Author: Don-vip Last Changed Date: 2015-05-07 01:27:41 +0200 (Thu, 07 May 2015) Build-Date: 2015-05-07 01:31:04 URL: http://josm.openstreetmap.de/svn/trunk Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last Changed Rev: 8338 Identification: JOSM/1.5 (8338 de) Windows 7 64-Bit Memory Usage: 329 MB / 3604 MB (33 MB allocated, but free) Java version: 1.8.0_45, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM Dataset consistency test: No problems found }}} " defect closed major Core latest duplicate template_report unicode