DynamicCodeLoggingService: avoid object churn
Recreating Matchers seems to incur a large memory cost until GC. Reuse the Matcher and reset it to avoid the worst of this. Test: atest DynamicCodeLoggerIntegrationTests Bug: 178402808 Change-Id: I959a5a6eb92366495cf343116636703d1e752742
Loading
Please register or sign in to comment