Random Adobe Animate Crash When Using .jsfl with fl.quit(false)

Hi Team,

Has anyone encountered the following issue when using Adobe Animate with a .jsfl file?

Error getting remote endpoint: asio.system:10057
(A request to send or receive data was disallowed because the socket is not connected and 
(when sending on a datagram socket using a sendto call) no address was supplied.)

handle_connect error: No connection could be made because the target machine actively refused it.

What I found:

I have a .jsfl file that contains only: fl.quit(false)

(Originally, the script included code to publish .fla files into .swf, but after investigating, I narrowed the issue down to fl.quit(false) and commented out everything else.)

Steps to Reproduce:

1. Create a test.jsfl file with only: fl.quit(false)
2. Open CMD and run: cd "C:\Program Files\Adobe\Adobe Animate 2024" Animate.exe "\\test.jsfl" -AlwaysRunJSFL
3. Animate will open, then close, and crash. This happens when fl.quit() is invoked—the Animate.exe process terminates, and the Adobe Crash Report window appears.
4. Now, comment out fl.quit(false);, run the command again, and manually close Animate. No crash occurs.

Additional Context:

Here’s the error I captured:

ERROR: Unable to start system bundle. (java.lang.ExceptionInInitializerError)
[info] asio async_connect error: asio.system:10061 (No connection could be made because the target machine actively refused it.)
[info] Error getting remote endpoint: asio.system:10057 (A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied.)

Has anyone seen this issue or found a workaround?
Since I don't know how fl.quit() function works, I am not sure why this method is throwing all those exceptions and where and what it tries to send.

To me the biggest issue is the Adobe Crash Report window (image attached)
I can just ignore the exception, but the window keeps popping up and waits user interactions.
Is there a way to completely disable it?