On Sat, 22 Mar 2025 02:12:48 GMT, Jay Bhaskar <jbhas...@openjdk.org> wrote:
> It is better to use dynamically calculated safe limit instead of a hardcoded > value like 250. The problem doesn't seem to be resource exhaustion. It seems that Apple is using a hard-coded number specifically to detect a potential case of infinite CFRunLoop recursion and fail early with a clear message rather than let the app run wild. This doesn't seem to be tied to any limit I can check dynamically. ------------- PR Comment: https://git.openjdk.org/jfx/pull/1741#issuecomment-2745395009
