Platform/Uptime: Difference between revisions

Platform/Uptime (view source)

417 bytes added , 27 May 2016

Add hangs as a crash report type, and provide a little more detail about process types.

Confirmed users, Bureaucrats and Sysops emeriti

1,217

edits

@@ Line 47: / Line 47: @@
 * Uncontrolled crashes: most commonly due to bad memory accesses, which are caused by bad pointers. Also sometimes illegal instructions, division-by-zero, etc.
 * Controlled aborts: e.g. due to MOZ_CRASH, MOZ_RELEASE_ASSERT, Rust panics, etc.
-* OOMs: running out of virtual or physical memory.
+* OOMs: running out of virtual or physical memory. These usually present as controlled aborts but contain additional annotations about the amount of memory being allocated.
+* Hangs: sometimes when a plugin or content process stops responding for too long, we will collect a dump from that process and then kill it.
-Crashes often halt Firefox execution. With e10s content process crashes are recoverable, though some or all tabs (depending on the number of content processes) need reloading. Plugin crashes are also recoverable.
+Crashes are grouped by process type:
+* "main" process crashes halt Firefox execution.
+* When a content process crashes, Firefox itself stays open but some or all tabs must be reloaded.
+* When an NPAPI plugin or Gecko media plugin crashes, the web page will stay alive but some functionality may be broken and require the user to reload pages which used that plugin.
 There are multiple different causes of crashes, multiple ways they can be identified and addressed, and multiple ways we can improve our processes for doing so.