No, sorry, on further testing, its not so simple. It seems its a random error, only when you do a bunch of tests do you see the pattern. So, I have run a minimal Lazarus app, a button on a form, 30 times. For comparison, I also run my app, a Lazarus GTK2 16K lines of code, also 30 times.
On U20.04.1 'out of the box' -
* Minimal Laz app - failed 20 out of 30 runs.
* tomboy-ng app - did not fail in 30 runs.
On U20.04-1 with all updates available on 23 September -
* Minimal Laz app - failed 5 out of 30 runs.
* tomboy-ng app - did not fail in 30 runs.
On U20.04-1 with all updates available on 23 September and appmenu-gtk2-module -
* Minimal Laz app - failed 14 out of 30 runs.
* tomboy-ng app - did not fail in 30 runs.
So, this raises some very worrying questions -
* Thirty runs seems enough to draw a reasonable conclusion that something has improved between the release of U20.04.1 and now. But while its an improvement, it has not solved the problem completely.
* Appmenu-gtk2-module does not solve the problem, may indeed make it worse ?
* My much more complicated application does not seem to suffer from this issue.
tomboy-ng is a little unconventional in that its first unit is not an LCL unit, it has no GUI aspect, it examines the command line arguments and if certain ones are there, it does whatever is requested and exits, all without a GUI appearing. In a more usual startup, that first unit starts the GUI units.
It also has a lot more things happening, obviously, but that startup seems a bit likely to be the difference ???
Anyone care to comment, please ?
Davo