Special Characters on Mac OS freezes keyboard

[zlavergne]

What steps will reproduce the problem?

1. Open anything with a text box.
2. On a Mac, hold down a character and use a special character
3. Try to continue typing (no input will be recognized)

What is the expected result?

It's expected that you can keep typing after using a special character.

What happens instead?

You are unable to type and must close the dialog box.

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

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2018-11-28 01:09:01 +0100 (Wed, 28 Nov 2018)
Build-Date:2018-11-28 00:26:41
Revision:14460
Relative:URL: ^/trunk

Identification: JOSM/1.5 (14460 en) Mac OS X 10.14.1
OS Build number: Mac OS X 10.14.1 (18B75)
Memory Usage: 715 MB / 1820 MB (191 MB allocated, but free)
Java version: 1.8.0_191-b12, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Screen: Display 188945160 1920x1080, Display 69748638 2048x1152
Maximum Screen Size: 2048x1152
VM arguments: [-Djava.security.policy=file:<java.home>/lib/security/javaws.policy, -DtrustProxy=true, -Djnlpx.home=<java.home>/bin, -Djava.security.manager, -Djnlpx.origFilenameArg=${HOME}/Library/Application Support/Oracle/Java/Deployment/cache/6.0/56/1ee8cfb8-632a3a0e, -Djnlpx.remove=false, -Dsun.awt.warmup=true, -Djava.util.Arrays.useLegacyMergeSort=true, -Djnlpx.heapsize=NULL,2048m, -Dmacosx.jnlpx.dock.name=JOSM, -Dmacosx.jnlpx.dock.icon=${HOME}/Library/Application Support/Oracle/Java/Deployment/cache/6.0/25/4c122699-396cdd98.icns, -Djnlp.application.href=https://josm.openstreetmap.de/download/josm.jnlp , -Djnlpx.jvm="<java.home>/bin/java"]
Dataset consistency test: No problems found

Plugins:
+ Mapillary (v1.5.17)
+ OpenStreetCam (168)
+ apache-commons (34506)
+ apache-http (34632)
+ auto_tools (67)
+ buildings_tools (34724)
+ ejml (34389)
+ geotools (34513)
+ graphview (34576)
+ jaxb (34506)
+ jna (34633)
+ jts (34524)
+ log4j (34527)
+ opendata (34698)
+ osm-obj-info (49)
+ routing (34554)
+ turnrestrictions (34643)
+ utilsplugin2 (34506)

Map paint styles:
+ /Volumes/Clingstone/JOSM Paint Styles and Presets/Kaart Styles 3.1.mapcss
+ https://josm.openstreetmap.de/josmfile?page=Styles/Lane_and_Road_Attributes&zip=1
+ /Volumes/Clingstone/JOSM Paint Styles and Presets/Overlapping Ways.mapcss

Validator rules:
+ ${HOME}/Downloads/kaart.validator.mapcss

Last errors/warnings:
- W: Failed to load Mappaint styles from '/Volumes/Clingstone/JOSM Paint Styles and Presets/Kaart Styles 3.1.mapcss'. Exception was: java.nio.file.NoSuchFileException: /Volumes/Clingstone/JOSM Paint Styles and Presets/Kaart Styles 3.1.mapcss
- E: java.nio.file.NoSuchFileException: /Volumes/Clingstone/JOSM Paint Styles and Presets/Kaart Styles 3.1.mapcss
- E: java.nio.file.NoSuchFileException: /Volumes/Clingstone/JOSM Paint Styles and Presets
- W: Initializing map style /Volumes/Clingstone/JOSM Paint Styles and Presets/Kaart Styles 3.1.mapcss completed in 123 ms (1 errors, 0 warnings)
- W: Failed to load Mappaint styles from '/Volumes/Clingstone/JOSM Paint Styles and Presets/Overlapping Ways.mapcss'. Exception was: java.nio.file.NoSuchFileException: /Volumes/Clingstone/JOSM Paint Styles and Presets/Overlapping Ways.mapcss
- E: java.nio.file.NoSuchFileException: /Volumes/Clingstone/JOSM Paint Styles and Presets/Overlapping Ways.mapcss
- E: java.nio.file.NoSuchFileException: /Volumes/Clingstone/JOSM Paint Styles and Presets
- W: Initializing map style /Volumes/Clingstone/JOSM Paint Styles and Presets/Overlapping Ways.mapcss completed in 1 ms (1 errors, 0 warnings)
- W: No configuration settings found.  Using hardcoded default values for all pools.

[GerdP]

@team: I see the same problem on my Windows laptop. I think it happens when key chattering happens, maybe in combination with a mouse event caused by accidentially touching the mousepad. Sometimes only the keyboard is ignored, sometimes JOSM stops to react completely showing minimal CPU usage. Maybe we can somehow mock that situation to find out what is wrong?

[zlavergne]

Possibly related to #13160. The workaround Here works when we have the above problem.