first 1000 line of the log file, the reset is mostly the infinite loop of message above.

Deleted: chrome.log 112 KB

chrome.log 112 KB View Download

Elijah, can you find an owner for this? It seems pretty bad.

I don't think we changed anything here recently in mustash land.

(hmmm Why are we always dumping arc logs at vlog=1 level ?)

We set the flag (thank you, Luis, for help me find this):
https://chromium.git.corp.google.com/chromiumos/platform2/+/3a5d607d1c2d425562dabb5e44821f6f73129363/login_manager/chrome_setup.cc#428

Luis, can you look at the instance_holder one at least?  Seems like something is repeatedly trying to get an interface that doesn't exist.  Can we either fix this broken pattern or reduce/remove the log?

+kpschoedel for the event rewriter log (cursory git blame implicates you)

#5 — There are two preconditions for the ‘Device ID’ message:

1. Processing a keystroke (one for each message, so, something is handing it keystrokes at that rate).

2. |ui::InputDeviceManager| does not include that device in |GetKeyboardDevices()|, or (probably less likely) does not exist.

I've been away from this for a couple years, but my first guess would be an input device, maybe a simulated volume key, that is not correctly registered with InputManager and is repeating continuously.

Mitigation for the audio bridge spam: https://chromium-review.googlesource.com/c/549195/

Although there's probably something else that needs to be fixed to avoid spamming ArcAudioBridge::SendVolumeState() to begin with.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a986cb967239b43e68109063b8a4a8174d9d4149

commit a986cb967239b43e68109063b8a4a8174d9d4149
Author: Luis Hector Chavez <lhchavez@google.com>
Date: Mon Jun 26 23:49:40 2017

arc: Avoid logspam in the audio bridge

This mitigates a runaway logging loop by avoiding to acquire the
instance when we know it won't be possible to acquire.

BUG= 736011 
TEST=Could not repro, but it should produce less spam

Change-Id: I24642d799baebf7ea1a8dd5abcc759e97c2efc37
Reviewed-on: https://chromium-review.googlesource.com/549195
Commit-Queue: Luis Hector Chavez <lhchavez@chromium.org>
Reviewed-by: Hidehiko Abe <hidehiko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#482470}
[modify] https://crrev.com/a986cb967239b43e68109063b8a4a8174d9d4149/components/arc/audio/arc_audio_bridge.cc
[modify] https://crrev.com/a986cb967239b43e68109063b8a4a8174d9d4149/components/arc/audio/arc_audio_bridge.h

Someone (not me, possibly ARC) should identify (a) why there are continuously repeating volume keystrokes, and/or (b) why the source device isn't correctly described by InputDeviceManager.

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This bug has an owner, thus, it's been triaged. Changing status to "assigned".