|
@@ -5,7 +5,6 @@ import {getLogger} from "jitsi-meet-logger";
|
5
|
5
|
import RTCBrowserType from "../RTC/RTCBrowserType";
|
6
|
6
|
|
7
|
7
|
var XMPPEvents = require('../../service/xmpp/XMPPEvents');
|
8
|
|
-var GlobalOnErrorHandler = require("../util/GlobalOnErrorHandler");
|
9
|
8
|
var MediaType = require('../../service/RTC/MediaType');
|
10
|
9
|
var VideoType = require('../../service/RTC/VideoType');
|
11
|
10
|
var Resolutions = require("../../service/RTC/Resolutions");
|
|
@@ -346,10 +345,15 @@ export default class ConnectionQuality {
|
346
|
345
|
type: STATS_MESSAGE_TYPE,
|
347
|
346
|
values: data });
|
348
|
347
|
} catch (e) {
|
349
|
|
- let errorMsg = "Failed to broadcast local stats";
|
350
|
|
- logger.error(errorMsg, e);
|
351
|
|
- GlobalOnErrorHandler.callErrorHandler(
|
352
|
|
- new Error(errorMsg + ": " + e));
|
|
348
|
+ // We often hit this in the beginning of a call, before the data
|
|
349
|
+ // channel is ready. It is not a big problem, because we will
|
|
350
|
+ // send the statistics again after a few seconds, and the error is
|
|
351
|
+ // already logged elsewhere. So just ignore it.
|
|
352
|
+
|
|
353
|
+ //let errorMsg = "Failed to broadcast local stats";
|
|
354
|
+ //logger.error(errorMsg, e);
|
|
355
|
+ //GlobalOnErrorHandler.callErrorHandler(
|
|
356
|
+ // new Error(errorMsg + ": " + e));
|
353
|
357
|
}
|
354
|
358
|
}
|
355
|
359
|
|