-
Joe Downing authored
I am working on some ETW stuff for Chrome Remote Desktop and I noticed that this parameter is unused and a default value of 16KB is always used. This isn't a big deal as the only caller appears to be its unit tests but it seemed like the value passed in should do something. The other approach would be to remove the param but adjusting the buffer size seems like a reasonable thing to expose (assuming the param is actually used). The issue in the previous CL was that the unittests requested a buffer size of 100MB but the max size is 1MB for realtime logging. The try-bots didn't detect the failure so I'll make sure this passes on the ASAN bots before submitting. This is an updated reland of: https://chromium-review.googlesource.com/c/chromium/src/+/2511290 Change-Id: I73bff2493f2ffcee6195faed7b4ab82d119259b2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2516886 Commit-Queue: Bruce Dawson <brucedawson@chromium.org> Auto-Submit: Joe Downing <joedow@chromium.org> Reviewed-by:
Bruce Dawson <brucedawson@chromium.org> Cr-Commit-Position: refs/heads/master@{#823707}
6c46059f