On Fri, 7 Feb 2025 18:41:53 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 18:41:53 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 21:49:24 GMT, Kevin Rushforth wrote:
> A better solution might be to set the max heap to 1Gb in the system tests
> project in `build.gradle`.
created https://bugs.openjdk.org/browse/JDK-8349679
-
PR Comment: https://git.openjdk.org/jfx/pull/1698#issuecomment-264
On Fri, 7 Feb 2025 21:38:15 GMT, Andy Goryachev wrote:
> I see the problem with gradle (I was running it in Eclipse). We apparently
> set -Xmx512m which is simply inadequate. We should at least double that, or
> even go to 2GB.
>
> Where is it being set?
The default is set by the gradle insta
On Fri, 7 Feb 2025 18:41:53 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 18:41:53 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 18:41:53 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 18:41:53 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
