On Thu, 4 Mar 2021 22:09:55 GMT, Phil Race <p...@openjdk.org> wrote: > I guess this is OK and yes we should have been checking this. > Not sure we really got to the bottom of the real world problem because I'd > expect the 2nd call just milliseconds after the first. But it could be that > this happens during some system updates and we get one printer reconfigured > message followed by another ..
Most of the time, the crash happens when a client reconnects to their active session where a JVM is already running. On reconnect, the list of printers is synced with the local printers on the client. In such a scenario, other software could also update its list of printers as well as repaint its UI. If the system is under high load, it's not impossible to have a long enough pause between the calls. ------------- PR: https://git.openjdk.java.net/jdk/pull/2836
