id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
13283	Loading an OSM file causes cpu load to hit 100%, permanently	alexkemp	floscher	"==== What steps will reproduce the problem?
1. Load latest snapshot + update plugins
2. Load saved .osm file (newark_sherwood.osm 64.9 MB (64,891,585 bytes))
3. Attempt to navigate to a BoundaryLine, and watch as load increases to 100%

==== What is the expected result?
Able to edit in normal fashion

==== What happens instead?
The only way to exit was to press on/off switch on box (just like using WinXP all over again)

==== Please provide any additional information below. Attach a screenshot if possible.
Sorry, but in the circumstances it is impossible to provide any further info, other than I recently loaded a 500+MB OSM-file & the system worked, just slowly. However, that was with 'tested', not 'latest'.

{{{
URL:http://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2016-08-04 23:55:20 +0200 (Thu, 04 Aug 2016)
Build-Date:2016-08-05 01:35:41
Revision:10733
Relative:URL: ^/trunk

Identification: JOSM/1.5 (10733 en_GB) Linux Debian GNU/Linux 8.5 (jessie)
Memory Usage: 314 MB / 1636 MB (224 MB allocated, but free)
Java version: 1.8.0_91-8u91-b14-1~bpo8+1-b14, Oracle Corporation, OpenJDK 64-Bit Server VM
Java package: openjdk-8-jre:amd64-8u91-b14-1~bpo8+1
VM arguments: [-Djosm.restart=true, -Djosm.home=<josm.pref>, -Djava.net.useSystemProxies=true]

Plugins:
+ DirectUpload (32329)
+ Mapillary (32639)
+ apache-commons (32584)
+ apache-http (32584)
+ buildings_tools (32728)
+ continuosDownload (53)
+ terracer (32426)
}}}
"	defect	closed	normal		Plugin mapillary	latest	fixed	template_report