buildings_tools v31895 rapidly degrades whilst JOSM is open

[alexkemp]

What steps will reproduce the problem?

1. Open JOSM_9979 (Java 1.8.0_77)
2. Draw 4 buildings using the buildings_tool_31895
3. Attempt to draw a 5th building

What is the expected result?

(mouse-click 1): beginning of a way
(mouse-click 2): establishment of a way at the angle desired
(mouse-click 3): completed building at angle & size desired

What happens instead?

(mouse-click 1): (i) beginning of a way, or:

(ii) beginning of a rectangle

(mouse-click 2): (if (i) for mc1): the tool only allows discrete angles

(as illustration, "0°, 90°, 180°", though actual angle-steps are much smaller than that)

(if (ii) for mc2): the tool completes 'normally', though the figure on the screen is a rectangle & NOT a line.

(mouse-click 2): (if (i) for mc1): (this step is never completed, as it is impossible to accurately draw a building over the top of the Bing image)

Please provide any additional information below. Attach a screenshot if possible.

Behaviour of this kind is normally the precursor to an eventual JOSM crash.
I have learnt to restart JOSM immediately when it begins to display this behaviour.
This is the first time that it has started to display such behaviour so quickly. I normally have to draw many more buildings than 4 before the problem begins.

URL:http://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2016-03-13 01:17:21 +0100 (Sun, 13 Mar 2016)
Build-Date:2016-03-13 02:35:00
Revision:9979
Relative:URL: ^/trunk

Identification: JOSM/1.5 (9979 en_GB) Linux Debian GNU/Linux 8.3 (jessie)
Memory Usage: 211 MB / 247 MB (66 MB allocated, but free)
Java version: 1.8.0_77-b03, Oracle Corporation, Java HotSpot(TM) Client VM
VM arguments: [-Djava.net.useSystemProxies=true]
Dataset consistency test: No problems found

Plugins:
- DirectUpload (30762)
- HouseNumberTaggingTool (31772)
- buildings_tools (31895)
- continuosDownload (1446070193)
- imagery_offset_db (32046)
- imageryadjust (31772)
- terracer (31895)
- utilsplugin2 (32099)

[Don-vip]

Replying to alexkemp:

Memory Usage: 211 MB / 247 MB (66 MB allocated, but free)

You were running JOSM with very low memory for this bug report. I guess you have increased it by now, is the problem still reproducible?

[alexkemp]

System memory was >1GB at the time. Are you suggesting that the issue was a JOSM memory leak?

I haven't done any mappping nor used JOSM for a very long time. I therefore have zero knowledge on the current state of the game.

[Don-vip]

JOSM bug report indicates that only 247 MB was allocated to JOSM. I don't know why, but clearly JOSM cannot work properly with so little memory.

For example, this is what my JOSM instance shows:
Memory Usage: 648 MB / 3634 MB (219 MB allocated, but free)

Please reopen if the problem persists and the status report indicates the JVM allows enough memory (1 GB or more).