Clear the stack-trace memory to avoid UTF-8 encoding problems #1543
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lemnik
force-pushed
the
PLAT-7701/clear-notify-stacktrace
branch
from
5600cfe
to
2dd97f3
Compare
Android notifier sizes
Generated by 🚫 Danger |
kattrali
reviewed
Dec 7, 2021
lemnik
force-pushed
the
PLAT-7701/clear-notify-stacktrace
branch
from
2dd97f3
to
470677f
Compare
…ors in `bugsnag_notify_env` [full ci]
lemnik
force-pushed
the
PLAT-7701/clear-notify-stacktrace
branch
from
470677f
to
11c4bd9
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Goal
Ensure that
bugsnag_notify_envdoes not fail due to uninitialised memory in the captured stack trace.Testing
Added a new function to the native mazerunner scenarios which will "dirty" the stack to emulate the behaviour of a longer running application. The function simply populates a 1Mb temporary array with data and returns.