ddyer0

I suppose it might be the case that there's a race between the EDT getting running and this process, but you can see it is running under CallSeriallyAndWait, so whatever...

You're wrong. I started with the Launch class provided by the application wizard. This is a very occasional problem starting up, 99% of the time it has no glitches.

Some other bits: it's happening with a variety of client hardware. I can't swear that it never happened before your recent changes to repaint/layout, but it's the kind of thing...

First occurred on 1/15, the log file that contains 1/15/2020 goes back to 10/14/2019, 9 occurrences since 1/15

here's Lanch.java ````java package com.boardspace; import lib.BSDate; import lib.G; import lib.Http; import lib.NullLayout; import online.common.OnlineConstants; import util.JWSApplication; import vnc.UDPService; import bridge.Color; import bridge.Frame; import bridge.FullScreen; import bridge.Panel; import bridge.Config; import...

So far, only on real android devices. I imagine with a good theory about the exact sequence of events, it would be possible to use breakpoints to induce it in...

One more note about this; at the point where the offending component is being added, a splash screen is being presented and removed in a separate thread - so tweaks...

Not enough to be definitive yet, but I changed the frame.dispose() in the example splash screen to frame.remove() and that seems to have fixed the problem. This isn't the first...

Here's another data point, which occurred in a version which does not use "dispose()", at a later point in the process when the initial "login" screen is being swapped for...

Here's another entry for your menagerie of "rare" crashes in the guts of your window implementation. Note that from the timestamps, these are two separate events. 23:32:14 :200 0 guest#3...