Suppress "errors" that aren't really errors.

remoting/webapp/remoting.js

Index: remoting/webapp/remoting.js
diff --git a/remoting/webapp/remoting.js b/remoting/webapp/remoting.js
index bcd29a24c8ac5d51970663dd59723d631fa97150..2fb14f93a96a99f0dfd23766d5d0fb3ade153c7b 100644
--- a/remoting/webapp/remoting.js
+++ b/remoting/webapp/remoting.js
@@ -46,6 +46,13 @@ remoting.init = function() {
   remoting.toolbar = new remoting.Toolbar(
       document.getElementById('session-toolbar'));
   remoting.clipboard = new remoting.Clipboard();
+  remoting.suspendMonitor = new remoting.SuspendMonitor(
+      function() {
+        if (remoting.clientSession) {
+          remoting.clientSession.logErrors(false);

[Wez, 2012/08/07 00:01:00]

The assumption is that once we've suspended there is no way that this session
will ever resume?

[Jamie, 2012/08/07 00:37:04]

Yes. We don't invoke the callback unless the device was idle for at least 2m,
and I think the number of connections that survive that and subsequently fail
for unrelated reasons is not likely to be statistically significant.

+        }
+      }
+  );
 
   remoting.oauth2.getEmail(remoting.onEmail, remoting.showErrorMessage);