profile-viewer 0.0.2 → 0.0.4

data/dist/8846b19a497771fe0e9d.svg

@@ -0,0 +1,4 @@
+<!-- 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 xmlns="http://www.w3.org/2000/svg" width="12" height="12" viewBox="0 0 16 16"><path fill="#000" d="M14.354 2.353l-.708-.707a2.007 2.007 0 0 0-2.828 0l-.379.379a.5.5 0 0 0 0 .707l2.829 2.829a.5.5 0 0 0 .707 0l.379-.379a2.008 2.008 0 0 0 0-2.829zM9.732 3.439a.5.5 0 0 0-.707 0L3.246 9.218a1.986 1.986 0 0 0-.452.712l-1.756 4.39A.5.5 0 0 0 1.5 15a.5.5 0 0 0 .188-.037l4.382-1.752a1.966 1.966 0 0 0 .716-.454l5.779-5.778a.5.5 0 0 0 0-.707zM5.161 12.5l-2.549 1.02a.1.1 0 0 1-.13-.13L3.5 10.831a.1.1 0 0 1 .16-.031l1.54 1.535a.1.1 0 0 1-.039.165z"></path></svg>

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,themeColor:"#0a84ff",noCompileLinks:[".*\\.svg"]};
+window.$docsify={name:"Firefox Profiler",auto2top:!0,loadSidebar:!0,loadNavbar:!0,subMaxLevel:2,themeColor:"#0a84ff",noCompileLinks:[".*\\.svg",".*\\.png"]};

data/dist/docs/memory-allocations.md

@@ -1,10 +1,11 @@
 # Memory Allocations
 
-The Firefox Profiler supports three different types of memory profiling
+The Firefox Profiler supports different types of memory profiling
 
 1. Memory Track
-2. Native Allocations (experimental)
-3. JavaScript Allocations (experimental)
+2. Native Allocations
+3. JavaScript Allocations
+4. Valgrind DHAT Profiles
 
 ## Memory Track
 
@@ -14,9 +15,9 @@ The memory track graphs overall allocation and deallocation numbers over time fo
 
 The graph visualization tracks the relative memory usage over the committed range of time. It's important to note that this is not absolute memory usage. The graph and numbers will change when committing a range selection.
 
-## Native Memory Allocations (experimental)
+## Native Memory Allocations
 
-The profiler has experimental support for analyzing allocations in native code (C++ and Rust) via stack sampling. These features require Nightly. To follow along you can open this [example showing DevTools opening and closing](https://perfht.ml/2LKZsfY)
+The profiler has support for analyzing allocations in native code (C++ and Rust) via stack sampling. These features require Nightly. To follow along you can open this [example showing DevTools opening and closing](https://perfht.ml/2LKZsfY)
 
 The Native Allocations feature works by collecting the stack and size of memory allocations from native (C++ or Rust) code. It does not collect every allocation, but only samples a subset of them. The sampling is biased towards larger allocations and larger frees. Larger allocations are more likely show up in the profile, and will most likely be more representative of the actual memory usage. Keep in mind that since these allocations are only sampled, not all allocations will be recorded. This means that memory track (the orange graph at the top) will most likely report different numbers for memory usage.
 
@@ -63,8 +64,29 @@ This option shows all of the deallocations that were sampled. Keep in mind that
 
 Some components inside of Gecko may implement their own memory management systems, and bypass the usage of system-level functions like `malloc` that are instrumented with this feature. For instance, some code could create a large buffer, and manage its own memory inside of that buffer. This feature would know about the allocation of the larger chunk of memory, but not how smaller allocations could be created inside of that buffer of memory. If this happens, information could be missing or misleading.
 
-## JavaScript Allocations (experimental)
+## JavaScript Allocations
 
 There is also a JavaScript-only allocation feature. This may be less useful as it only samples the creation of JS objects, and does not track garbage collection or frees. In fact, the Native Allocations feature is a superset of the JavaScript allocations feature, and includes the JavaScript stack information. Enable this through the `Features` section of the popup.
 
 ![A screenshot of the call tree showing JS.](images/allocation-js.png)
+
+## Valgrind's "Dynamic Heap Analysis Tool" DHAT
+
+When working outside of Firefox, you can use [Valgrind's DHAT tool](https://valgrind.org/docs/manual/dh-manual.html). DHAT has its own viewer, but it lacks some of the visualization and filtering capabilities of the Firefox Profiler. The converted profile will lack some of the finer details like read, write, and access information, but it does contain the amount of bytes allocated. On a Linux system (or even a Linux docker image), you can install it via:
+
+```sh
+sudo apt-get install valgrind
+```
+
+Then run your command:
+
+```
+valgrind --tool=dhat ./my-program
+```
+
+A dhat profile will be output in the same directory as your program: `dhat.out.<pid>`. Drag that file into the profiler to view it. There will be 4 tracks containing the memory information. Only the call tree and flame graph are supported.
+
+ * **Bytes at End** - Allocations that were never freed when the program ended.
+ * **Bytes at Global Max** - Bytes allocated when the global heap size peaked.
+ * **Maximum Bytes** - The maximum bytes allocated at that call site at one time.
+ * **Total Bytes** - The total bytes allocated over the course of the program.

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><link rel="preload" href="locales/en-US/app.ftl" as="fetch"/><link rel="icon" href="/favicon.png"><script defer="defer" src="/main.fc4f388a376c68dab444.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="/favicon.png"><script defer="defer" src="/main.89ba95fadf0fbee4977a.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/be/app.ftl

@@ -373,8 +373,8 @@ MarkerSidebar--select-a-marker = Выберыце маркер, каб пагл
 
 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.
@@ -754,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,
@@ -838,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.
 

data/dist/locales/de/app.ftl

@@ -30,6 +30,7 @@ AppHeader--github-icon =
 ## AppViewRouter
 ## This is used for displaying errors when loading the application.
 
+AppViewRouter--error-from-post-message = Das Profil konnte nicht importiert werden.
 AppViewRouter--error-unpublished = Das Profil von { -firefox-brand-name } konnte nicht abgerufen werden.
 AppViewRouter--error-from-file = Die Datei konnte nicht gelesen oder das darin enthaltene Profil nicht verarbeitet werden.
 AppViewRouter--error-local = Noch nicht implementiert.
@@ -169,6 +170,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.
@@ -278,6 +319,15 @@ Home--load-files-from-other-tools2 =
     <perf>Linux perf</perf>, <simpleperf>Android SimplePerf</simpleperf>, die
     Chrome Performance Panel, <androidstudio>Android Studio</androidstudio> oder
     eine Datei im <dhat>dhat-Format</dhat> oder <traceevent>Googles Trace-Event-Format</traceevent>. <write>Erfahren Sie, wie Sie Ihren eigenen Importeur schreiben</write>.
+Home--install-chrome-extension = Installieren Sie die Chrome-Erweiterung
+Home--chrome-extension-instructions =
+    Verwenden Sie die <a>{ -profiler-brand-name }-Erweiterung für Chrome</a>,
+    um Leistungsprofile in Chrome zu erfassen und im { -profiler-brand-name }
+    zu analysieren. Installieren Sie die Erweiterung aus dem Chrome Web Store.
+Home--chrome-extension-recording-instructions =
+    Verwenden Sie nach der Installation das Symbolleisten-Symbol der Erweiterung
+    oder die Tastenkombinationen zum Starten und Stoppen der Profilerstellung. Sie können auch
+    Profile exportieren und hier zur detaillierten Analyse laden.
 
 ## IdleSearchField
 ## The component that is used for all the search inputs in the application.
@@ -371,8 +421,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.
@@ -611,6 +661,7 @@ ProfileFilterNavigator--full-range-with-duration = Vollständiger Zeitraum ({ $f
 
 ## Profile Loader Animation
 
+ProfileLoaderAnimation--loading-from-post-message = Das Profil wird importiert und verarbeitet…
 ProfileLoaderAnimation--loading-unpublished = Das Profil wird direkt von { -firefox-brand-name } importiert…
 ProfileLoaderAnimation--loading-from-file = Datei lesen und Profil verarbeiten…
 ProfileLoaderAnimation--loading-local = Noch nicht implementiert.
@@ -686,6 +737,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 +760,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 +789,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 +816,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 +888,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.