On Fri, 7 Feb 2025 23:00:37 GMT, Andy Goryachev wrote:
>> ## Root Cause
>> Animation gets started in a background thread, which causes the animation
>> handler to run in the FX application thread, thus creating simultaneous
>> access to the control's fields (list of children in this case).
>>
On Mon, 10 Feb 2025 17:03:49 GMT, Andy Goryachev wrote:
> You are probably right about `System.gc()` being called too often. I would
> say though that the purpose of this test is to uncover initialization issues
> rather than finding other problems with the controls, so it's probably ok as
> i
On Fri, 7 Feb 2025 23:00:37 GMT, Andy Goryachev wrote:
>> ## Root Cause
>> Animation gets started in a background thread, which causes the animation
>> handler to run in the FX application thread, thus creating simultaneous
>> access to the control's fields (list of children in this case).
>>
On Fri, 7 Feb 2025 23:00:37 GMT, Andy Goryachev wrote:
>> ## Root Cause
>> Animation gets started in a background thread, which causes the animation
>> handler to run in the FX application thread, thus creating simultaneous
>> access to the control's fields (list of children in this case).
>>
> ## Root Cause
> Animation gets started in a background thread, which causes the animation
> handler to run in the FX application thread, thus creating simultaneous
> access to the control's fields (list of children in this case).
>
> ## Solution
> Postpone the animation unless running in the F
