UnsupportedOperationException: Proposed rect has such extreme aspect ratio that it would be zero-width at preferredZoom

[Frans S]

What steps will reproduce the problem?

1. just opened JOSM from OSMmap
2. get error directly

What is the expected result?

What happens instead?

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

URL:http://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2017-09-02 14:47:18 +0200 (Sat, 02 Sep 2017)
Build-Date:2017-09-02 20:53:16
Revision:12712
Relative:URL: ^/trunk

Identification: JOSM/1.5 (12712 en) Windows 10 64-Bit
OS Build number: Windows 10 Enterprise 1703 (15063)
Memory Usage: 179 MB / 989 MB (57 MB allocated, but free)
Java version: 1.8.0_144-b01, Oracle Corporation, Java HotSpot(TM) Client VM
Screen: \Display0 1680x1050, \Display1 1680x1050
Maximum Screen Size: 1680x1050
Dataset consistency test: No problems found

Plugins:
+ FastDraw (33583)
+ ShapeTools (1220)
+ auto_tools (1494971731)
+ buildings_tools (33004)
+ markseen (4)
+ measurement (33088)
+ touchscreenhelper (32699)
+ turnrestrictions (33537)
+ utilsplugin2 (33579)

Tagging presets:
+ https://josm.openstreetmap.de/josmfile?page=Presets/HotNepal&zip=1

Map paint styles:
- https://github.com/hotosm/HDM-JOSM-style/archive/master.zip
+ https://github.com/MarkCupitt/HOT-Osm-Validation/blob/master/HOT-Validate.mapcss
- https://josm.openstreetmap.de/josmfile?page=Styles/Fixme&zip=1

Last errors/warnings:
- E: Handled by bug report queue: java.lang.UnsupportedOperationException: Proposed rect has such extreme aspect ratio that it would be zero-width at preferredZoom


=== REPORTED CRASH DATA ===
BugReportExceptionHandler#handleException:
No data collected.

Warning issued by: BugReportExceptionHandler#handleException

=== STACK TRACE ===
Thread: pool-1-thread-1 (50)
java.lang.UnsupportedOperationException: Proposed rect has such extreme aspect ratio that it would be zero-width at preferredZoom
	at org.openstreetmap.josm.plugins.markseen.QuadTreeNode.markBoundsSeen(QuadTreeNode.java:489)
	at org.openstreetmap.josm.plugins.markseen.QuadTreeMeta$MarkBoundsSeenRequest.run(QuadTreeMeta.java:122)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

[ris]

Hmm yes I was never expecting this to happen under normal use. I was probably being overzealous in throwing such an extreme error when it's actually a relatively harmless condition (it will just fail to record this rectangle).

What I'll probably do is change this to being a logged but non-fatal error unless assertions are enabled (for the tests). Sorry for the inconvenience, you may like to disable the plugin for now if it's happening repeatedly.

Thanks for the report though. Incidentally, were you zoomed very far out? Far in?

[ris]

This should be fixed in the latest version of markseen. Please update and give it a go.