Confirmed users
423
edits
Crash reporting overhaul: Difference between revisions
Jump to navigation
Jump to search
Updated the status of several projects
(Flagged several projects as in-progress) |
(Updated the status of several projects) |
||
| Line 112: | Line 112: | ||
== Crash monitor == | == Crash monitor == | ||
Status: | Status: in progress<br> | ||
Developer(s): gsvelto<br> | Developer(s): gsvelto<br> | ||
Source code:<br> | Source code:<br> | ||
| Line 165: | Line 165: | ||
== Crash reporter client == | == Crash reporter client == | ||
Status: | Status: completed<br> | ||
Developer(s): afranchuk<br> | Developer(s): afranchuk<br> | ||
Source code: | Source code: https://searchfox.org/mozilla-central/source/toolkit/crashreporter/client | ||
Original source code:<br> | Original source code:<br> | ||
* https://hg.mozilla.org/mozilla-central/file/6f0a8dddad51/toolkit/crashreporter/client | * https://hg.mozilla.org/mozilla-central/file/6f0a8dddad51/toolkit/crashreporter/client | ||
| Line 209: | Line 209: | ||
* We should leverage Rust's asynchronous facility to make processing non-blocking and the UI responsive | * We should leverage Rust's asynchronous facility to make processing non-blocking and the UI responsive | ||
* We should add platform-independent tests for the parts of the code that do not require UI interaction | * We should add platform-independent tests for the parts of the code that do not require UI interaction | ||
=== Results === | |||
The new crash reporter client is built around a simple platform-indepented UI | |||
Rust library which wraps the individual platform-specific widgets. This made | |||
the UI code almost completely platform-independent as opposed to the old | |||
implementation which was entirely platform dependent, effectively requiring | |||
three different indepented implementations. Additionally the new client is | |||
extensively covered in tests and has more robust networking. Integration of | |||
more features such as Glean-based crash pings and Necko-based networking is | |||
now possible. | |||
== Glean-based crash pings == | == Glean-based crash pings == | ||
| Line 258: | Line 269: | ||
== minidump-analyzer == | == minidump-analyzer == | ||
Status: | Status: completed<br> | ||
Developer(s):<br> | Developer(s):<br> | ||
Source code: https://github.com/rust-minidump/rust-minidump/<br> | Source code: https://github.com/rust-minidump/rust-minidump/<br> | ||
| Line 312: | Line 323: | ||
Sentry is already working on integrating symbolic with rust-minidump so we're | Sentry is already working on integrating symbolic with rust-minidump so we're | ||
currently waiting it out. This might require very little work in the end. | currently waiting it out. This might require very little work in the end. | ||
=== Results === | |||
The new client-side minidump analyzer supports all our tier 1 and tier 2 | |||
architectures with full support for native deubg information, is significantly | |||
more robust than the old one, extensively covered with tests and provide stacks | |||
that are consistent with our server-side stack walker. Additionally the crates | |||
used by the stack walker machinery are shared with the profiler reducing the | |||
maintaince burden and yielding consistent results across the two projects. | |||
= Server-side tools and components = | = Server-side tools and components = | ||