You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, there's code to catch panics and display them as error dialogs, but it only runs in debug mode. Is there a significant performance or binary size cost to enabling this in release mode as well? There are many benefits of doing so:
Many debug builds run quite slowly. Being able to debug panics with fast release builds would be helpful.
If you don't use debug builds at all because they're so slow, you may not even be aware that the panic handler exists and is a very helpful debugging tool. I only learned about it when you mentioned it in Parameters' UI flags cannot be modified in-place #6.
If an effect panics and it is caught, users can save their work instead of having After Effects instantly crash and lose it all.
Displaying the panic message in the dialog box allows users to file more descriptive bug reports that point to the offending code.
The text was updated successfully, but these errors were encountered:
I haven't benchmarked it, but I just did that to make sure to not any additional overhead, since generally the plugins are performance critical. I think we can make that the default feature flag, available to turn off by the plugin author if necessary
Looks like catch_unwind is not great for performance so I don't think adding it by default is a good idea in this case. Instead, I documented it in the README advising to add change optimization level of the debug builds.
I added the panic handler as an optional feature ("catch-panics")
Right now, there's code to catch panics and display them as error dialogs, but it only runs in debug mode. Is there a significant performance or binary size cost to enabling this in release mode as well? There are many benefits of doing so:
The text was updated successfully, but these errors were encountered: