Skip to content

Tags: licolin/orbit

Tags

1.65

Toggle 1.65's commit message
Fix file name conflict issue

And sequence number to file name if file already
exists.

Test: Manual - press x many times see that files with suffixes are
      created
Bug: http://b/191247811

1.64

Toggle 1.64's commit message
Set pretty(demangled)_name when constructing FunctionInfo from Instru…

…mentedFunction

Bug: http://b/189222632
Test: run capture on OrbitTestLegacyApi

1.63

Toggle 1.63's commit message
Fix crash when hovering on manually instrumented async scope

TimerInfo::kApiEvent don't have an "InstrumentedFunction" associated
with them so don't expect one.

Test: profile OrbitTest with manual instrumentation enabled, hover on
a profiling scope in one of the "async" tracks.

1.62

Toggle 1.62's commit message
Clear viewport dirty flag before rendering

This allows the GlCanvas::Draw() method to update the viewport, which
will correctly mark it as dirty again and trigger a new rendering next
frame.

1.61

Toggle 1.61's commit message
Capture() now waits for the Dialog to disappear

(cherry picked from commit 99c86ee18e768194af5bfb4d502cca9296e07f12)

1.60

Toggle 1.60's commit message
Hide SourcePathsMapping button behing feature flag

1.59

Toggle 1.59's commit message
Fix crash on unhooking function when capture_data is not available

Test: Start Orbit, load preset, unhook a function,
      make sure there is no crash.
Bug: http://b/179787649

1.58

Toggle 1.58's commit message
Update orbit_tracks E2E test

Some tracks are not present on the devkit which fails the test. Changed
the MatchTracks test to handle "or" options for tracks and adjusted the
list of tracks.

1.57

Toggle 1.57's commit message
Merge remote-tracking branch 'origin/release/1.56' into merge_back

1.56

Toggle 1.56's commit message
Fix issues with frame tracks when loading a capture

When loading a capture, Orbit can be in a state where hooking a function
that has hits in the "Live" tab must not be allowed, either because
Orbit is not in a connected state (no process selected) or because the
module to which the function belongs is not loaded. In both these cases,
the "Hook" option is disabled in the "Live" context menu, however it was
incorrectly possible to hook a function by enabling a frame track. In
the connected state, this leads to a crash when taking a capture with
the incorrectly hooked function.

We now apply the same check that is used for enabling the "Hook" context
menu entry when enabling the frame track for a function to make sure
it's only hooked when possible.

Bug: http://b/174296341

Tested: Manual tests for the cases described on the bug.