profile-viewer 0.0.1 → 0.0.3

data/dist/_headers

@@ -15,7 +15,6 @@
 
   # 1. script-src
   #   a. 'wasm-unsafe-eval' allows to execute wasm scripts without compromising the javascript CSP.
-  #   b. We use Google Analytics to track the usage of the application.
   # 2. style-src
   #   a. `unsafe-inline` is necessary to support favicons.
   #   b. Google Fonts are used in the docs.
@@ -26,7 +25,7 @@
   # 7. `frame-ancestors` is the same purpose as `X-Frame-Options` above.
   # 8. `form-action`prevents forms, we don't need this.`
   # 9. `frame-src` allows the embedding of YouTube videos in the docs.
-  Content-Security-Policy: default-src 'self'; script-src 'self' 'wasm-unsafe-eval' https://www.google-analytics.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src http: https: data:; object-src 'none'; connect-src *; frame-ancestors 'self'; form-action 'none'; frame-src www.youtube-nocookie.com
+  Content-Security-Policy: default-src 'self'; script-src 'self' 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src http: https: data:; object-src 'none'; connect-src *; frame-ancestors 'self'; form-action 'none'; frame-src www.youtube-nocookie.com
 
 # Set the correct MIME type for WebAssembly modules.
 /*.wasm

data/dist/contribute.json

@@ -1,37 +1,33 @@
 {
-    "name": "Firefox profiler",
-      "description": "Web app for Firefox performance analysis",
-      "repository": {
-        "url": "https://github.com/firefox-devtools/profiler",
-        "license": "MPL2",
-        "tests": "https://circleci.com/gh/firefox-devtools/profiler"
-      },
-      "participate": {
-        "home": "https://github.com/firefox-devtools/profiler/blob/main/CONTRIBUTING.md",
-        "docs": "https://github.com/firefox-devtools/profiler/tree/main/docs-developer",
-        "matrix": "https://chat.mozilla.org/#/room/#profiler:mozilla.org",
-        "chat": {
-          "url": "https://chat.mozilla.org/#/room/#profiler:mozilla.org",
-          "contacts": [
-            "@julienw:mozilla.org",
-            "@canova:mozilla.org",
-            "@mstange:mozilla.org",
-            "@davehunt:mozilla.org"
-          ]
-        }
-      },
-      "bugs": {
-        "list": "https://github.com/firefox-devtools/profiler/issues",
-        "report": "https://github.com/firefox-devtools/profiler/issues/new",
-        "mentored": "https://github.com/firefox-devtools/profiler/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22"
-      },
-      "urls": {
-        "prod": "https://profiler.firefox.com",
-        "stage": "https://main--perf-html.netlify.app/"
-      },
-      "keywords": [
-        "performance",
-        "firefox",
-        "web"
+  "name": "Firefox profiler",
+  "description": "Web app for Firefox performance analysis",
+  "repository": {
+    "url": "https://github.com/firefox-devtools/profiler",
+    "license": "MPL2",
+    "tests": "https://circleci.com/gh/firefox-devtools/profiler"
+  },
+  "participate": {
+    "home": "https://github.com/firefox-devtools/profiler/blob/main/CONTRIBUTING.md",
+    "docs": "https://github.com/firefox-devtools/profiler/tree/main/docs-developer",
+    "matrix": "https://chat.mozilla.org/#/room/#profiler:mozilla.org",
+    "chat": {
+      "url": "https://chat.mozilla.org/#/room/#profiler:mozilla.org",
+      "contacts": [
+        "@julienw:mozilla.org",
+        "@canova:mozilla.org",
+        "@mstange:mozilla.org",
+        "@davehunt:mozilla.org"
       ]
-  }
+    }
+  },
+  "bugs": {
+    "list": "https://github.com/firefox-devtools/profiler/issues",
+    "report": "https://github.com/firefox-devtools/profiler/issues/new",
+    "mentored": "https://github.com/firefox-devtools/profiler/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22"
+  },
+  "urls": {
+    "prod": "https://profiler.firefox.com",
+    "stage": "https://main--perf-html.netlify.app/"
+  },
+  "keywords": ["performance", "firefox", "web"]
+}

data/dist/d6df0017c0241dfe86ff.svg

@@ -0,0 +1,6 @@
+<!-- This Source Code Form is subject to the terms of the Mozilla Public
+   - License, v. 2.0. If a copy of the MPL was not distributed with this
+   - file, You can obtain one at http://mozilla.org/MPL/2.0/. -->
+<svg width="24" height="24" fill="none" xmlns="http://www.w3.org/2000/svg">
+    <path fill-rule="evenodd" clip-rule="evenodd" d="M12 2C6.477 2 2 6.477 2 12s4.477 10 10 10 10-4.477 10-10S17.523 2 12 2zM9.731 4.066a8.257 8.257 0 0 0-5.938 7.09h3.266a13.027 13.027 0 0 1 2.672-7.09zm-2.672 8.84h-3.26a8.258 8.258 0 0 0 5.873 7.01 13.025 13.025 0 0 1-2.613-7.01zm4.911 7.01a11.295 11.295 0 0 1-3.157-7.01h6.369a11.296 11.296 0 0 1-3.212 7.01zm-3.157-8.76a11.298 11.298 0 0 1 3.217-7.072 11.299 11.299 0 0 1 3.161 7.072H8.813zm8.132 0a13.027 13.027 0 0 0-2.616-7.073 8.257 8.257 0 0 1 5.878 7.073h-3.262zm-.008 1.75a13.026 13.026 0 0 1-2.669 7.028 8.257 8.257 0 0 0 5.933-7.028h-3.264z" fill="#000" />
+</svg>

data/dist/docs/_sidebar.md

@@ -15,6 +15,7 @@
   * [Perf profiling on Linux](./guide-perf-profiling.md)
   * [Perf profiling on Android](./guide-android-profiling.md)
   * [IPC Messages](./ipc-messages.md)
+  * [Profiler control using POSIX signals](./async-posix-signal-control.md)
 * [Video Tutorials](./videos.md)
   * [Firefox Profiler intro](./videos-intro.md)
   * [Samples and markers](./videos-samples-markers.md)

data/dist/docs/advanced-topics.md

@@ -7,3 +7,4 @@ developers of the Firefox browser.
 * [Perf profiling on Linux](./guide-perf-profiling.md)
 * [Perf profiling on Android](./guide-android-profiling.md)
 * [IPC Messages](./ipc-messages.md)
+* [Profiler control using POSIX signals](./async-posix-signal-control.md)

data/dist/docs/async-posix-signal-control.md

@@ -0,0 +1,102 @@
+
+# Profiler control using POSIX signals
+
+The Firefox profiler supports the use of asynchronous POSIX signals for a
+limited number of operations, specifically starting and stopping the profiler.
+This can be useful in situations where the normal UI or keyboard shortcut
+control of the profiler is not available.
+
+In brief, a user can send the POSIX signal `SIGUSR1` to the main Firefox process
+to start the profiler, and the signal `SIGUSR2` to stop the profiler. Upon
+recieiving the "stop" signal, the profiler will collect the current profile data
+and write it to a `.json` file in the user's downloads directory. For example,
+on MacOS:
+
+    // Send signal USR1 to the first (main) process of Firefox.app to start the profiler
+    kill -s USR1 `pgrep -f Firefox.app | head -n 1`
+    // wait for firefox to gather some data
+    sleep 10
+    // Send signal USR2 to the same process to stop the profiler
+    kill -s USR2 `pgrep -f Firefox.app | head -n 1`
+    // Find the result in the download folder
+    ls ~/Downloads/ | grep "profile.*json"
+
+From there, the user can open the written profile using the standard profiler
+UI, by navigating to [profiler.firefox.com](https://profiler.firefox.com), and selecting
+"Load a profile from file".
+
+Typically, sending a signal to a program is done using the `kill`
+[command](https://man7.org/linux/man-pages/man1/kill.1.html), as seen in the
+above example. It is important to specify the correct signal, as the default is
+`TERM`, which will terminate the program. For the profiler, only signals
+`SIGUSR1` (for starting) and `SIGUSR2` (for stopping) should be used. Note that they
+are written without the `SIG` prefix when used as an argument to `kill` i.e.:
+
+    kill -s USR1 <firefox pid>      // start the profiler
+    kill -s USR2 <firefox pid>      // stop the profiler
+
+    // Alternative syntax
+    kill -USR1 <firefox pid>
+    kill --signal USR1 <firefox pid>
+
+!> Only the process ID of the "main" process should be used. Child processes are
+controlled by the parent process via IPC, and are unable to write their
+processes to disk (due to sandboxing restrictions), so are not useful to profile
+using signals.
+
+The process ID of a running instance of Firefox can be found in a number of
+ways, for instance:
+
+    pgrep -f Firefox.app      // On MacOS
+    pidof Firefox             // on Linux
+
+In case of confusion, the main process is typically the one with lowest ID, when
+sorted numerically.
+
+Signal support is intended as a last-ditch debugging tool for situations where
+we want to be able to diagnose issues with Firefox, but may not be able to use
+the existing UI controls or Keyboard shortcuts to start/stop the profiler. For
+example, if we encounter a prolonged freeze while browsing, it may be useful to
+capture a profile by using POSIX signals to start and stop the profiler.
+
+In a "normal" profiling flow, the resulting profile is communicated to the
+profiler front-end directly, and then displayed to the user at the end of a
+profiling session. The signal-controlled profiler bypasses this flow, and
+instead writes a profile to disk. This makes it possible for us to debug in
+situations where we may not be able to access the profiler UI in the same
+session of firefox as the one we are debugging, with the small added friction of
+needing to directly load the profile.
+
+## Limitations
+
+The current implementation of POSIX signal support has a number of important
+limitations that potential users need to be aware of:
+
+* The profiler currently uses a set of "default"
+  [values](https://searchfox.org/mozilla-central/rev/7a8904165618818f73ab7fc692ace4a57ecd38c9/tools/profiler/core/platform.cpp#633)
+  when started using signals. There are currently plans to support configuration
+  (see [Bug 1866007](https://bugzilla.mozilla.org/show_bug.cgi?id=1866007) for
+  further information).
+* Async signal handling is currently only supported and tested on POSIX native
+  platforms, i.e. Linux and MacOS. Support for Windows is planned, but not yet
+  implemented (see [Bug
+  1867328](https://bugzilla.mozilla.org/show_bug.cgi?id=1867328) for further
+  information).
+* The "stop" signal must be sent to Firefox's "main" process. This is due to
+  Firefox's sandboxing rules, which disallow non-main processes (in general)
+  from opening file handles. Because of this, individual processes cannot dump
+  their own data to disk, so cannot individually handle the stop signal.
+* Signal support in the Firefox profiler is incompatible with Firefox's [code
+  coverage](https://firefox-source-docs.mozilla.org/tools/code-coverage/index.html)
+  tooling, as both rely on the same POSIX signals (`SIGUSR1` and `SIGUSR2`). In
+  an ideal world we could use Linux's
+  [real-time](https://man7.org/linux/man-pages/man7/signal.7.html) signals
+  instead, as they offer a much larger set of user-defined signals that would
+  not clash with the signals used by the code coverage tool. Unfortunately,
+  MacOS does not support these signals, so we are limited to the smaller set of
+  signals in order to support a wider set of platforms.
+* Although signals are used to start/stop the profiler, the aggregation of
+  content-process profiles is still done using "traditional" Firefox IPC calls.
+  If, therefore, you are using signals to diagnose issues with a "stuck" main
+  thread in the main process, Firefox may not be able to aggregate child content
+  process profiles.

data/dist/docs/guide-startup-shutdown.md

@@ -40,7 +40,7 @@ If you have compiled GeckoView-example locally, you can launch it with `./mach r
 ```bash
 ./mach run --setenv MOZ_PROFILER_STARTUP=1 \
            --setenv MOZ_PROFILER_STARTUP_INTERVAL=5 \
-           --setenv MOZ_PROFILER_STARTUP_FEATURES=threads,js,stackwalk,leaf,screenshots,ipcmessages,java \
+           --setenv MOZ_PROFILER_STARTUP_FEATURES=js,stackwalk,screenshots,ipcmessages,java,processcpu,cpu \
            --setenv MOZ_PROFILER_STARTUP_FILTERS="GeckoMain,Compositor,Renderer,IPDL Background"
 ```
 
@@ -50,7 +50,7 @@ Alternatively, if you have installed GeckoView-example from another source, you
 adb shell am start -n org.mozilla.geckoview_example/.App \
     --es env0 MOZ_PROFILER_STARTUP=1 \
     --es env1 MOZ_PROFILER_STARTUP_INTERVAL=5 \
-    --es env2 MOZ_PROFILER_STARTUP_FEATURES=threads,js,stackwalk,leaf,screenshots,ipcmessages,java \
+    --es env2 MOZ_PROFILER_STARTUP_FEATURES=js,stackwalk,screenshots,ipcmessages,java,processcpu,cpu \
     --es env3 MOZ_PROFILER_STARTUP_FILTERS="GeckoMain,Compositor,Renderer,IPDL Background"
 ```
 
@@ -58,15 +58,15 @@ adb shell am start -n org.mozilla.geckoview_example/.App \
 
 Fenix has a [different way](https://firefox-source-docs.mozilla.org/mobile/android/geckoview/consumer/automation.html#reading-configuration-from-a-file) to specify environment variables: it uses a yaml file.
 
-The easiest way to set up startup profiling is to run the `<fenix-repo>/tools/setup-startup-profiling.py` script. For example:
+The easiest way to set up startup profiling is to run the `<mozilla-central-repo>/mobile/android/fenix/tools/setup-startup-profiling.py` script. For example:
 ```bash
-./tools/setup-startup-profiling.py activate nightly  # To activate startup profiling on nightly.
-./tools/setup-startup-profiling.py deactivate beta  # To deactivate startup profiling on beta.
+./mobile/android/fenix/tools/setup-startup-profiling.py activate nightly  # To activate startup profiling on nightly.
+./mobile/android/fenix/tools/setup-startup-profiling.py deactivate beta  # To deactivate startup profiling on beta.
 ```
 
 If the app is uninstalled or the device is restarted, the `activate` command may need to be re-run. The script is hard-coded to use a default configuration file with default profiling arguments. If you wish to change these arguments or use a non-standard app ID, modify the script locally or read below.
 
-If you don't want to check out [the fenix repository](https://github.com/mozilla-mobile/fenix/), you should be able to download [the script standalone](https://raw.githubusercontent.com/mozilla-mobile/fenix/master/tools/setup-startup-profiling.py) and execute it.
+If you don't want to check out [mozilla-central](https://hg.mozilla.org/mozilla-central/), you should be able to download [the script standalone](https://hg.mozilla.org/mozilla-central/raw-file/tip/mobile/android/fenix/tools/setup-startup-profiling.py) and execute it.
 
 #### Manual configuration
 
@@ -78,7 +78,7 @@ The filename of the YAML file mentioned above depends on the bundle ID of your F
     env:
       MOZ_PROFILER_STARTUP: 1
       MOZ_PROFILER_STARTUP_INTERVAL: 5
-      MOZ_PROFILER_STARTUP_FEATURES: threads,js,stackwalk,leaf,screenshots,ipcmessages,java
+      MOZ_PROFILER_STARTUP_FEATURES: js,stackwalk,screenshots,ipcmessages,java,processcpu,cpu
       MOZ_PROFILER_STARTUP_FILTERS: GeckoMain,Compositor,Renderer,IPDL Background
     ```
  2. Push this file to the device with `adb push org.mozilla.fenix-geckoview-config.yaml /data/local/tmp/`.

data/dist/docs/js/init.js

@@ -1 +1 @@
-window.$docsify={name:"Firefox Profiler",auto2top:!0,loadSidebar:!0,loadNavbar:!0,subMaxLevel:2,ga:"UA-35433268-81",themeColor:"#0a84ff",noCompileLinks:[".*\\.svg"]};
+window.$docsify={name:"Firefox Profiler",auto2top:!0,loadSidebar:!0,loadNavbar:!0,subMaxLevel:2,themeColor:"#0a84ff",noCompileLinks:[".*\\.svg",".*\\.png"]};

data/dist/index.html

@@ -1 +1 @@
-<!doctype html><html lang="en"><head><meta charset="utf-8"><meta name="viewport" content="initial-scale=1"/><title>Firefox Profiler</title><script src="/before-load.js"></script><link rel="icon" href="/favicon.png"><script defer="defer" src="/main.8208fda2d35ddbe38d55.bundle.js"></script></head><body style="background-color: #363959; /* ink-70 */"><div id="root"></div><div id="root-overlay"></div></body></html>
+<!doctype html><html lang="en"><head><meta charset="utf-8"/><meta name="viewport" content="initial-scale=1"/><title>Firefox Profiler</title><link rel="preload" href="locales/en-US/app.ftl" as="fetch"/><link rel="icon" href="/sidekiq/profile-viewer/favicon.png"><script defer="defer" src="/sidekiq/profile-viewer/main.ac7130d34ce3b872712a.bundle.js"></script></head><body style="background-color: #363959; /* ink-70 */"><div id="root"></div><div id="root-overlay"></div></body></html>

data/dist/locales/README.md

@@ -6,6 +6,7 @@ Please change only the locale content in the `en-US`
 directory. The other directories are changed using [Pontoon](https://pontoon.mozilla.org/projects/firefox-profiler/).
 
 Here are the most important rules:
+
 1. If you change the string in a way that changes the meaning, you need to
    change the string key as well. If that doesn't change the meaning (for
    example, if that's a typo fix), then the string key can stay the same. You

data/dist/locales/be/app.ftl

@@ -232,7 +232,7 @@ FullTimeline--tracks-button = Дарожак: <span>{ $visibleTrackCount }</span
 ## Home page
 
 Home--upload-from-file-input-button = Загрузіць профіль з файла
-Home--upload-from-url-button = Загрузіце профіль з URL
+Home--upload-from-url-button = Загрузіць профіль з URL
 Home--load-from-url-submit-button =
     .value = Загрузіць
 Home--documentation-button = Дакументацыя
@@ -322,7 +322,7 @@ ListOfPublishedProfiles--uploaded-profile-information-list =
 ## This is used as a context menu for the Marker Chart, Marker Table and Network
 ## panels.
 
-MarkerContextMenu--set-selection-from-duration = Наладзьце выбарку на аснове працягласці маркера
+MarkerContextMenu--set-selection-from-duration = Наладзіць выбарку на аснове працягласці маркера
 MarkerContextMenu--start-selection-here = Пачаць вылучэнне тут
 MarkerContextMenu--end-selection-here = Скончыць вылучэнне тут
 MarkerContextMenu--start-selection-at-marker-start = Пачаць вылучэнне ад <strong>пачатку</strong> маркера
@@ -345,25 +345,36 @@ MarkerContextMenu--select-the-receiver-thread = Выберыце паток-ат
 #   $threadName (String) - Name of the thread that will be selected.
 MarkerContextMenu--select-the-sender-thread = Выберыце паток-адпраўнік “<strong>{ $threadName }</strong>”
 
+## MarkerFiltersContextMenu
+## This is the menu when filter icon is clicked in Marker Chart and Marker Table
+## panels.
+
+# This string is used on the marker filters menu item when clicked on the filter icon.
+# Variables:
+#   $filter (String) - Search string that will be used to filter the markers.
+MarkerFiltersContextMenu--drop-samples-outside-of-markers-matching = Адкідваць сэмплы па-за межамі маркераў, якія адпавядаюць «<strong>{ $filter }</strong>»
+
 ## MarkerSettings
 ## This is used in all panels related to markers.
 
 MarkerSettings--panel-search =
     .label = Фільтр маркераў:
     .title = Паказваць толькі маркеры, якія адпавядаюць пэўнаму імені
+MarkerSettings--marker-filters =
+    .title = Фільтры маркераў
 
 ## MarkerSidebar
 ## This is the sidebar component that is used in Marker Table panel.
 
-MarkerSidebar--select-a-marker = Выберыце маркер, каб паглядзець інфармацыі пра яго.
+MarkerSidebar--select-a-marker = Выберыце маркер, каб паглядзець інфармацыю пра яго.
 
 ## MarkerTable
 ## This is the component for Marker Table panel.
 
 MarkerTable--start = Пачатак
 MarkerTable--duration = Працягласць
-MarkerTable--type = Тып
-MarkerTable--description = Апісанне
+MarkerTable--name = Назва
+MarkerTable--details = Падрабязнасці
 
 ## MenuButtons
 ## These strings are used for the buttons at the top of the profile viewer.
@@ -457,6 +468,8 @@ MenuButtons--metaInfo--logical-cpu =
         [few] { $logicalCPUs } лагічных ядра
        *[many] { $logicalCPUs } лагічных ядзер
     }
+MenuButtons--metaInfo--profiling-started = Запіс пачаўся:
+MenuButtons--metaInfo--profiling-session = Працягласць запісу:
 MenuButtons--metaInfo--main-process-started = Асноўны працэс пачаўся:
 MenuButtons--metaInfo--main-process-ended = Асноўны працэс скончыўся:
 MenuButtons--metaInfo--interval = Інтэрвал:
@@ -476,6 +489,7 @@ MenuButtons--metaInfo--buffer-duration-seconds =
 MenuButtons--metaInfo--buffer-duration-unlimited = Неабмежавана
 MenuButtons--metaInfo--application = Праграма
 MenuButtons--metaInfo--name-and-version = Назва і версія:
+MenuButtons--metaInfo--application-uptime = Час працы:
 MenuButtons--metaInfo--update-channel = Канал абнаўлення:
 MenuButtons--metaInfo--build-id = ID зборкі:
 MenuButtons--metaInfo--build-type = Тып зборкі:
@@ -740,7 +754,6 @@ TrackNameButton--hide-process =
 
 TrackMemoryGraph--relative-memory-at-this-time = адносная памяць на гэты момант
 TrackMemoryGraph--memory-range-in-graph = дыяпазон памяці ў графіку
-TrackMemoryGraph--operations-since-the-previous-sample = аперацый, пачынаючы з папярэдняга ўзору
 
 ## TrackPower
 ## This is used to show the power used by the CPU and other chips in a computer,
@@ -824,6 +837,25 @@ TrackPower--tooltip-energy-carbon-used-in-preview-milliwatthour = { $value } м
 TrackPower--tooltip-energy-carbon-used-in-preview-microwatthour = { $value } мкВт·гад ({ $carbonValue } мг CO₂e)
     .label = Энергія, якая спажываецца ў бягучай выбарцы
 
+## TrackBandwidth
+## This is used to show how much data was transfered over time.
+## For the strings in this group, the carbon dioxide equivalent is estimated
+## from the amount of data transfered.
+## The carbon dioxide equivalent represents the equivalent amount
+## of CO₂ to achieve the same level of global warming potential.
+
+# This is used in the tooltip of the bandwidth track.
+# Variables:
+#   $value (String) - the value for the data transfer speed.
+#                     Will contain the unit (eg. B, KB, MB)
+TrackBandwidthGraph--speed = { $value } у секунду
+    .label = Хуткасць перадачы для гэтай выбаркі
+# This is used in the tooltip of the bandwidth track.
+# Variables:
+#   $value (String) - how many read or write operations were performed since the previous sample
+TrackBandwidthGraph--read-write-operations-since-the-previous-sample = { $value }
+    .label = аперацый уводу/вываду з часу папярэдняй выбаркі
+
 ## TrackSearchField
 ## The component that is used for the search input in the track context menu.
 
@@ -896,6 +928,10 @@ TransformNavigator--collapse-direct-recursion-only = Згарнуць тольк
 # Variables:
 #   $item (String) - Name of the function that transform applied to.
 TransformNavigator--collapse-function-subtree = Згарнуць паддрэва: { $item }
+# "Drop samples outside of markers matching ..." transform.
+# Variables:
+#   $item (String) - Search filter of the markers that transform will apply to.
+TransformNavigator--drop-samples-outside-of-markers-matching = Адкідваць сэмплы па-за межамі маркераў, якія адпавядаюць: “{ $item }”
 
 ## "Bottom box" - a view which contains the source view and the assembly view,
 ## at the bottom of the profiler UI

data/dist/locales/de/app.ftl

@@ -169,6 +169,46 @@ CallTree--inlining-badge = (inlined)
 ## This is the sidebar component that is used in Call Tree and Flame Graph panels.
 
 CallTreeSidebar--select-a-node = Wählen Sie einen Knoten aus, um Informationen darüber anzuzeigen.
+CallTreeSidebar--call-node-details = Details zum Aufrufknoten
+
+## CallTreeSidebar timing information
+##
+## Firefox Profiler stops the execution of the program every 1ms to record the
+## stack. Only thing we know for sure is the stack at that point of time when
+## the stack is taken. We try to estimate the time spent in each function and
+## translate it to a duration. That's why we use the "traced" word here.
+## There is actually no difference between "Traced running time" and "Running
+## time" in the context of the profiler. We use "Traced" to emphasize that this
+## is an estimation where we have more space in the UI.
+##
+## "Self time" is the time spent in the function itself, excluding the time spent
+## in the functions it called. "Running time" is the time spent in the function
+## itself, including the time spent in the functions it called.
+
+CallTreeSidebar--traced-running-time =
+    .label = Nachverfolgte Laufzeit
+CallTreeSidebar--traced-self-time =
+    .label = Nachverfolgte Eigenzeit
+CallTreeSidebar--running-time =
+    .label = Laufzeit
+CallTreeSidebar--self-time =
+    .label = Eigenzeit
+CallTreeSidebar--running-samples =
+    .label = Laufende Stichproben
+CallTreeSidebar--self-samples =
+    .label = Eigenstichproben
+CallTreeSidebar--running-size =
+    .label = Laufgröße
+CallTreeSidebar--self-size =
+    .label = Eigengröße
+CallTreeSidebar--categories = Kategorien
+CallTreeSidebar--implementation = Implementierung
+CallTreeSidebar--running-milliseconds = Laufende Millisekunden
+CallTreeSidebar--running-sample-count = Anzahl laufende Stichproben
+CallTreeSidebar--running-bytes = Laufende Bytes
+CallTreeSidebar--self-milliseconds = Eigene Millisekunden
+CallTreeSidebar--self-sample-count = Anzahl Eigenstichproben
+CallTreeSidebar--self-bytes = Eigene Bytes
 
 ## CompareHome
 ## This is used in the page to compare two profiles.
@@ -371,8 +411,8 @@ MarkerSidebar--select-a-marker = Wählen Sie eine Markierung aus, um Information
 
 MarkerTable--start = Beginn
 MarkerTable--duration = Dauer
-MarkerTable--type = Typ
-MarkerTable--description = Beschreibung
+MarkerTable--name = Name
+MarkerTable--details = Details
 
 ## MenuButtons
 ## These strings are used for the buttons at the top of the profile viewer.
@@ -686,6 +726,13 @@ TabBar--marker-table-tab = Markierungstabelle
 TabBar--network-tab = Netzwerk
 TabBar--js-tracer-tab = JS-Aufzeichnung
 
+## TabSelectorMenu
+## This component is a context menu that's opened when you click on the root
+## range at the top left corner for profiler analysis view. It's used to switch
+## between tabs that were captured in the profile.
+
+TabSelectorMenu--all-tabs-and-windows = Alle Tabs und Fenster
+
 ## TrackContextMenu
 ## This is used as a context menu for timeline to organize the tracks in the
 ## analysis UI.
@@ -702,6 +749,10 @@ TrackContextMenu--hide-other-screenshots-tracks = Andere Screenshots-Tracks ausb
 TrackContextMenu--hide-track = „{ $trackName }“ verbergen
 TrackContextMenu--show-all-tracks = Alle Tracks anzeigen
 TrackContextMenu--show-local-tracks-in-process = Alle Tracks in diesem Prozess anzeigen
+# This is used as the context menu item to hide all tracks of the selected track's type.
+# Variables:
+#   $type (String) - Name of the type of selected track to hide.
+TrackContextMenu--hide-all-tracks-by-selected-track-type = Alle Spuren vom Typ „{ $type }“ ausblenden
 # This is used in the tracks context menu as a button to show all the tracks
 # that match the search filter.
 TrackContextMenu--show-all-matching-tracks = Alle passenden Tracks anzeigen
@@ -727,7 +778,7 @@ TrackNameButton--hide-process =
 
 TrackMemoryGraph--relative-memory-at-this-time = Relativer Speicherverbrauch zu diesem Zeitpunkt
 TrackMemoryGraph--memory-range-in-graph = Speicherbereich im Diagramm
-TrackMemoryGraph--operations-since-the-previous-sample = Operationen seit der vorherigen Stichprobe
+TrackMemoryGraph--allocations-and-deallocations-since-the-previous-sample = Allokationen und Aufhebungen von Allokationen seit der vorherigen Stichprobe
 
 ## TrackPower
 ## This is used to show the power used by the CPU and other chips in a computer,
@@ -754,6 +805,21 @@ TrackPower--tooltip-power-watt = { $value } W
 #   $value (String) - the power value at this location
 TrackPower--tooltip-power-milliwatt = { $value } mW
     .label = Leistung
+# This is used in the tooltip when the power value uses the kilowatt unit.
+# Variables:
+#   $value (String) - the power value at this location
+TrackPower--tooltip-average-power-kilowatt = { $value } kW
+    .label = Durchschnittliche Leistung in der aktuellen Auswahl
+# This is used in the tooltip when the power value uses the watt unit.
+# Variables:
+#   $value (String) - the power value at this location
+TrackPower--tooltip-average-power-watt = { $value } W
+    .label = Durchschnittliche Leistung in der aktuellen Auswahl
+# This is used in the tooltip when the instant power value uses the milliwatt unit.
+# Variables:
+#   $value (String) - the power value at this location
+TrackPower--tooltip-average-power-milliwatt = { $value } mW
+    .label = Durchschnittliche Leistung in der aktuellen Auswahl
 # This is used in the tooltip when the energy used in the current range uses the
 # kilowatt-hour unit.
 # Variables:
@@ -811,6 +877,46 @@ TrackPower--tooltip-energy-carbon-used-in-preview-milliwatthour = { $value } mWh
 TrackPower--tooltip-energy-carbon-used-in-preview-microwatthour = { $value } µWh ({ $carbonValue } mg CO₂e)
     .label = In der aktuellen Auswahl verwendete Energie
 
+## TrackBandwidth
+## This is used to show how much data was transfered over time.
+## For the strings in this group, the carbon dioxide equivalent is estimated
+## from the amount of data transfered.
+## The carbon dioxide equivalent represents the equivalent amount
+## of CO₂ to achieve the same level of global warming potential.
+
+# This is used in the tooltip of the bandwidth track.
+# Variables:
+#   $value (String) - the value for the data transfer speed.
+#                     Will contain the unit (eg. B, KB, MB)
+TrackBandwidthGraph--speed = { $value } pro Sekunde
+    .label = Übertragungsgeschwindigkeit für diese Teilmenge
+# This is used in the tooltip of the bandwidth track.
+# Variables:
+#   $value (String) - how many read or write operations were performed since the previous sample
+TrackBandwidthGraph--read-write-operations-since-the-previous-sample = { $value }
+    .label = Lese-/Schreiboperationen seit der vorherigen Teilmenge
+# This is used in the tooltip of the bandwidth track.
+# Variables:
+#   $value (String) - the total of transfered data until the hovered time.
+#                     Will contain the unit (eg. B, KB, MB)
+#   $carbonValue (string) - the carbon dioxide equivalent (CO₂e) value in grams
+TrackBandwidthGraph--cumulative-bandwidth-at-this-time = { $value } ({ $carbonValue } g CO₂e)
+    .label = Bislang übertragene Daten
+# This is used in the tooltip of the bandwidth track.
+# Variables:
+#   $value (String) - the total of transfered data during the visible time range.
+#                     Will contain the unit (eg. B, KB, MB)
+#   $carbonValue (string) - the carbon dioxide equivalent (CO₂e) value in grams
+TrackBandwidthGraph--total-bandwidth-in-graph = { $value } ({ $carbonValue } g CO₂e)
+    .label = Im sichtbaren Bereich übertragene Daten
+# This is used in the tooltip of the bandwidth track when a range is selected.
+# Variables:
+#   $value (String) - the total of transfered data during the selected time range.
+#                     Will contain the unit (eg. B, KB, MB)
+#   $carbonValue (string) - the carbon dioxide equivalent (CO₂e) value in grams
+TrackBandwidthGraph--total-bandwidth-in-range = { $value } ({ $carbonValue } g CO₂e)
+    .label = In der aktuellen Auswahl übertragene Daten
+
 ## TrackSearchField
 ## The component that is used for the search input in the track context menu.