RFR: 8357157: Exception thrown from AnimationTimer freezes application [v2]

[Andy Goryachev]

On Sat, 17 May 2025 12:21:17 GMT, Michael Strauß <mstrauss at openjdk.org> wrote:

>> On the other hand, AnimationTimer is a public API that allows for arbitrary code execution, which always has the potential to fail for any number of reasons (think of calling an unstable API from the timer callback). We can’t rule that out entirely. This is only a fallback in any case, as a well-tested application shouldn’t throw exceptions from timer callbacks in the first place.
>
> I've removed the system property, so there's a hard-coded limit of 100 exceptions now.

100 still looks excessive to me - it's unlikely that we'll have two different scenarios when this happens, so most of the time the log will have 100 identical traces.

I mean, one is probably enough, we could have 2 or 4 just to drive the message home.  Anything beyond 8 is simply annoying, don't you think?

-------------

PR Review Comment: https://git.openjdk.org/jfx/pull/1811#discussion_r2095993342