| commit | c0748d4a0af91ab1d0775dde6b860ce117438072 | [log] [tgz] |
|---|---|---|
| author | Brian Sheedy <bsheedy@chromium.org> | Thu Nov 11 01:01:14 2021 |
| committer | Catapult LUCI CQ <catapult-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Nov 11 21:19:34 2021 |
| tree | 6b41924d8c2a54c844adb263ac807fa099d8968a | |
| parent | 8d1435ba083e929b9f056af39c91ecc560a75110 [diff] |
[Telemetry] Workaround GC deadlock Works around a flaky deadlock that can occur (mainly under Python 3) during tracing shutdown after a test completes. This is caused when some objects with custom destructors (InspectorBackend is one known class, but there may be others) get garbage collected while tracing is being stopped, which causes garbage collection to deadlock attempting to acquire a tracing lock. This is worked around by manually garbage collecting just before shutting down tracing. Bug: chromium:1267210 Change-Id: I49ab9f189e6bb947c3bbbd654c60ad2e06f015cc Reviewed-on: https://chromium-review.googlesource.com/c/catapult/+/3273676 Auto-Submit: Brian Sheedy <bsheedy@chromium.org> Commit-Queue: John Chen <johnchen@chromium.org> Reviewed-by: John Chen <johnchen@chromium.org>
Catapult is the home for several performance tools that span from gathering, displaying and analyzing performance data. This includes:
These tools were created by Chromium developers for performance analysis, testing, and monitoring of Chrome, but they can also be used for analyzing and monitoring websites, and eventually Android apps.
Please see our contributor's guide