Wrong sorter usage when dowloading relation members

[naoliv]

I was downloading some relation members when I saw this in the console:

WARNING: row index is bigger than sorter's row count. Most likely this is a wrong sorter usage.

I don't know if it's inoffensive or if something should be changed in JOSM.
I also couldn't reproduce when downloading the same data again, in a new layer.

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2017-12-05 00:58:56 +0100 (Tue, 05 Dec 2017)
Revision:13194
Build-Date:2017-12-05 02:33:31
URL:http://josm.openstreetmap.de/svn/trunk

Identification: JOSM/1.5 (13194 pt_BR) Linux Debian GNU/Linux testing (buster)
Memory Usage: 1199 MB / 7168 MB (843 MB allocated, but free)
Java version: 9.0.1+11-Debian-1, Oracle Corporation, OpenJDK 64-Bit Server VM
Screen: :0.0 1600x900, :0.1 1280x1024
Maximum Screen Size: 1600x1024
Java package: openjdk-9-jre:amd64-9.0.1+11-1
Java ATK Wrapper package: libatk-wrapper-java:all-0.33.3-13
VM arguments: [--add-modules=java.activation,java.se.ee, -Dawt.useSystemAAFontSettings=on]
Dataset consistency test: No problems found

[Don-vip]

Can't reproduce, can you please post a step-by-step scenario?

[naoliv]

I saw it happening another time, but I still couldn't find a way to reproduce it.

[Don-vip]

I'm going to close it for now. Please reopen if you manage to reproduce.