Fix diagnostics crash in profile mode #53878
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When DiagnosticsNode is used in profile mode it crashed during FlutterErrorDetails construction.
This PR guards against null build.properties and emptyBodyDescription.
When web users encounter an exception in release builds, they use --profile to diagnose the issue. Without this fix they can't see the correct exception/stack trace.
Related Issues
#53487
Fixes: #54108
Tests
I added the following tests:
The test requires end to end test running in profile mode. PR for engine E2E test: flutter/engine#17492
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]). This will ensure a smooth and quick review process.///).flutter analyze --flutter-repo) does not report any problems on my PR.Breaking Change
Did any tests fail when you ran them? Please read [Handling breaking changes].