Details
-
Suggestion
-
Resolution: Unresolved
-
P3: Somewhat important
-
None
-
Qt Creator 4.11.0
-
None
-
PopOS 20.04
Installed though apt (latest version)
OS: Pop!_OS 20.04 LTS x86_64
Host: MS-7A63 1.0
Kernel: 5.4.0-7634-generic
Uptime: 2 days, 1 hour, 6 mins
Packages: 3825 (dpkg), 29 (snap)
Shell: bash 5.0.16
Resolution: 3840x2160
DE: GNOME
WM: Mutter
WM Theme: Pop
Theme: Pop-dark [GTK2/3]
Icons: Pop [GTK2/3]
Terminal: gnome-terminal
CPU: Intel i5-7600K (4) @ 4.200GHz
GPU: NVIDIA GeForce GTX 1060 6GB
Memory: 9585MiB / 15970MiBPopOS 20.04 Installed though apt (latest version) OS: Pop!_OS 20.04 LTS x86_64 Host: MS-7A63 1.0 Kernel: 5.4.0-7634-generic Uptime: 2 days, 1 hour, 6 mins Packages: 3825 (dpkg), 29 (snap) Shell: bash 5.0.16 Resolution: 3840x2160 DE: GNOME WM: Mutter WM Theme: Pop Theme: Pop-dark [GTK2/3] Icons: Pop [GTK2/3] Terminal: gnome-terminal CPU: Intel i5-7600K (4) @ 4.200GHz GPU: NVIDIA GeForce GTX 1060 6GB Memory: 9585MiB / 15970MiB
-
Linux/Wayland
Description
When Using the Chome tracing visual tool the timeline is very hard to read. If there is only one thread with multiple events. The longest event takes up the whole timeline and it's hard to select the subevent with in that longest event. Unless you go to statistics and click on the subevent to visualize it within the master event. This is kinda hard to explain, but I've linked a video to kinda showing some issue.
Basically what this boils down to. Make overlapping events on different lines so it's easier to see.