From 70b3e7d594425427ee8daac76db9eb48edc688ec Mon Sep 17 00:00:00 2001 From: "disher@chromium.org" Date: Sat, 2 Jun 2012 22:12:25 +0000 Subject: Chrome version of monitor configuration code New MonitorConfigurator class interprets events (ctrl-F4, display add/remove, and brightness-related CRTC state changes). Ctrl-F4 events come in through the AcceleratorController. Display add/remove events are interpretted by MonitorChangeObserverX11. CRTC enable/disable events related to power management come over DBus and are interpretted by the new OutputObserver class. Note the the chromeos/monitor/DEPS change can be removed once the now-unused code is retired from powerd (since that is the only reason for a DBus call-out). Valgrind suppressions.txt was updated because this change re-orders our initial XRR calls such that a different top-level call is blamed for its leak. BUG=chromium:126493 TEST=Manually tested with an additional display and mode switching on Lumpy. Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=140031 Review URL: https://chromiumcodereview.appspot.com/10384103 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140203 0039d316-1c4b-4281-b951-d872f2087c98 --- tools/valgrind/memcheck/suppressions.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'tools') diff --git a/tools/valgrind/memcheck/suppressions.txt b/tools/valgrind/memcheck/suppressions.txt index acaf3e0b..6e00830 100644 --- a/tools/valgrind/memcheck/suppressions.txt +++ b/tools/valgrind/memcheck/suppressions.txt @@ -630,13 +630,14 @@ fun:_vgnU_freeres } -# XRandRInfo object seems to be leaking inside XRRFindDisplay. +# XRandRInfo object seems to be leaking inside XRRFindDisplay. This happens the +# first time it is called, no matter who the caller is. We have observed this +# problem with both XRRSelectInput and XRRQueryExtension. { bug_119677 Memcheck:Leak fun:malloc fun:XRRFindDisplay - fun:XRRSelectInput } { Flash Player Leak -- cgit v1.1