id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
18075	JOSM slow with MapCSS on openSUSE systems	stoecker	team	"Hello,

today I did a bit of maxspeed mapping and used the maxspeed style.

As soon as following rule kicked in, JOSM became awfull slow:
{{{
#!mapcss
/* 6.3 - report conditional maxspeed without default maxspeed */
way[""maxspeed:conditional""][!""maxspeed""]::maxspeedlayer,
way[""maxspeed:forward:conditional""][!""maxspeed:forward""][!""maxspeed""]::maxspeedcasinglayer,
way[""maxspeed:backward:conditional""][!""maxspeed:backward""][!""maxspeed""]::maxspeedcasinglayer
{
        color: yellow;
        dashes-background-color: red;
        dashes: 4,24;
        opacity: 1;
        width: 5;
        text: tr(""conditional maxspeed without default maxspeed!"");
        text-color: black;
        font-size: 11;
        text-halo-color: red;
        text-halo-radius: 2;
        left-casing-width: 1;
        left-casing-color: yellow;
        right-casing-width: 1;
        right-casing-color: yellow;
        left-casing-opacity: 1;
        right-casing-opacity: 1;
        z-index: 1;
}
}}}

It seems the text rendering is causing an extreme slowdown. For some time now JOSM seems slow to me on openSUSE systems, but I couldn't nail down the reason. As far as I can see it independent from the java version, but for reference here is what I used (recent openSUSE Tumbleweed).

{{{
openjdk version ""1.8.0_212""
OpenJDK Runtime Environment (IcedTea 3.12.0) (build 1.8.0_212-b4 suse-2.2-x86_64)
OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)
}}}

To be able to use josm at all I disabled display of most area styles.

I'd appreciate if someone with a bit more skills in timing debugging could test openSUSE. If this is not a generic JOSM issue (which I don't believe, otherwise there would be much more complains) it must have a reason in something different in modern openSUSE distributions."	defect	new	normal		Core mappaint			performance	Don-vip Klumbumbus