New article "Crash analyzer tool" #3086
Open
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
mikehoffms
commented
Feb 29, 2024
|
|
||
| Use the **Crash analyzer** tool to analyze Microsoft Edge<!--todo: review/expand--> crashes. In the **Crash analyzer** tool, you can input a JavaScript stack trace, such as for non-fatal JavaScript exceptions, and then have your sourcemaps applied to the stack trace so that you can debug faster. | ||
|
|
||
| <!-- todo: show instead a demo page that's meant to cause crashes --> |
There was a problem hiding this comment.
show instead a relevant demo page that causes crashes
@captainbrosset
mikehoffms
changed the title
mikehoffms
changed the title
mikehoffms
commented
May 9, 2024
There was a problem hiding this comment.
Was the Crash Analyzer tool made for internal MS teams who get their stacktraces from Watson?
@robpaveza - from p.b.'s post
rendered article:
https://review.learn.microsoft.com/microsoft-edge/devtools-guide-chromium/crash-analyzer/index?branch=pr-en-us-3086
mikehoffms
commented
May 9, 2024
There was a problem hiding this comment.
Could you help us shape the story for 3P customers?
- How should we advise user to get crash stacktraces?
- Should they use this .md file's typescript code listing? Rendered: https://review.learn.microsoft.com/microsoft-edge/devtools-guide-chromium/crash-analyzer/?branch=pr-en-us-3086#producing-the-required-stack-trace-format (listing is from .doc)
- Where do the stacktraces end up; where can user copy the stacktrace from?
rendered article:
https://review.learn.microsoft.com/microsoft-edge/devtools-guide-chromium/crash-analyzer/index?branch=pr-en-us-3086
@robpaveza - questions from p.b.'s post
captainbrosset
requested changes
May 13, 2024
mikehoffms
commented
May 15, 2024
| Use the **Crash analyzer** tool to analyze and quickly diagnose crashes of your production web app. In the **Crash analyzer** tool, you can input a JavaScript stack trace, such as for non-fatal JavaScript exceptions, and then have your source maps applied to the stack trace so that you can debug faster. The **Crash analyzer** tool enables you to take a minified JavaScript stack trace and rapidly work backwards to determine what lines of code caused the error. | ||
|
|
||
|  | ||
| <!-- todo: Create new demo page & use it in this article. |
There was a problem hiding this comment.
Create demo webpage or app
mikehoffms
commented
May 15, 2024
mikehoffms
commented
May 15, 2024
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.
Rendered articles for review:
AB#49236474