stack_trace : Is there any potential issue with wrapping my app in Chain.capture()

[FlutterByte98]

Hi all!

I'm working on a Flutter app and want to improve my error reporting, especially for async errors. I came across the stack_trace package and its "Chain.capture()" method, which seems to provide much better stack traces across async boundaries.

The usage is to wrap your app's entry point like this:

Chain.capture(() {
runApp(MyApp());
}
This looks great for debugging and error reporting, but I'm wondering: Is there any potential downside or performance impact to wrapping my entire app in Chain.capture?

Would love to hear from anyone.
Thanks!

[lrhn]

Try it.

It will definitely have a performance impact, because it captures an extra stack trace at every asynchronous break.
How big and impact, and whether it matters for a UI-driven app, is something you can only answer by testing.

[FlutterByte98]

Try it.

It will definitely have a performance impact, because it captures an extra stack trace at every asynchronous break. How big and impact, and whether it matters for a UI-driven app, is something you can only answer by testing.

Well . Its an app aimed for the clients and its big. Testing the performance is tricky and costs work hours.

[FlutterByte98]

@lrhn ,Is there any way to test the "performance impact" ? Integration tests are not stable (take different times in each iteration), and manual testing won't give me any info.