On Fri, 7 Feb 2025 18:41:53 GMT, Andy Goryachev <ango...@openjdk.org> 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).
>>
>> ## Solution
>> Postpone the animation unless running in the FX application thread. There
>> is no functional difference if the component is created/used in the FX
>> application thread.
>
> Andy Goryachev has updated the pull request with a new target base due to a
> merge or a rebase. The incremental webrev excludes the unrelated changes
> brought in by the merge/rebase. The pull request contains two additional
> commits since the last revision:
>
> - Merge branch 'master' into 8349105.thread.safety.pagination
> - postpone animation
I still see the OOM. Are you running it from gradle? Here is the command line
that will reproduce it, after first building with: "`gradle sdk shims`":
gradle --info -PTEST_ONLY=true -PFULL_TEST=true -PUSE_ROBOT=true \
:systemTests:test --tests NodeInitializationStressTest.pagination
-------------
PR Comment: https://git.openjdk.org/jfx/pull/1698#issuecomment-2644134162
