wm: Avoid log spew in window manager logs.
On developer builds (where NDEBUG is not defined), the window
manager logs are growing uncontrollably. After a few days (Nov 17
though Nov 21), I've got almost a gigabyte of logs:
# du -sh /var/log/window_manager/
923M /var/log/window_manager/
This machine has really just been sitting at the login prompt.
After the initial bit of debug info, logs are filled with:
[1121/131449:21180773:INFO:opengles_visitor.cc(227)] Performing partial screen update: 405, 570, 23, 22.
[1121/131449:21181179:INFO:opengles_visitor.cc(267)] Visit container: stage
[1121/131449:21258991:INFO:opengles_visitor.cc(227)] Performing partial screen update: 405, 570, 23, 22.
[1121/131449:21259441:INFO:opengles_visitor.cc(267)] Visit container: stage
[1121/131449:21336403:INFO:opengles_visitor.cc(227)] Performing partial screen update: 405, 570, 23, 22.
[1121/131449:21336905:INFO:opengles_visitor.cc(267)] Visit container: stage
These messages aren't providing enough useful information to the
average user to justify such log spew. Deleting them so that we can
still keep other INFO-level logs around but don't get these ones.
NOTE that filling up /var/log so badly had the effect of
making all autotests take forever, so this should really help the
average developer.
BUG=None
TEST=Emerged and saw that log spew was gone.
Change-Id: I60d727bb8f37456a232d75aed8eabc5c59fdf0e0
Reviewed-on: https://gerrit.chromium.org/gerrit/12011
Tested-by: Doug Anderson <dianders@chromium.org>
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Commit-Ready: Doug Anderson <dianders@chromium.org>
Reviewed-by: Daniel Erat <derat@chromium.org>
1 file changed