W3C home > Mailing lists > Public > public-device-apis-log@w3.org > December 2016

[sensors] Don't allocate response objects to avoid triggering GC

From: Tobie Langel via GitHub <sysbot+gh@w3.org>
Date: Tue, 06 Dec 2016 10:58:17 +0000
To: public-device-apis-log@w3.org
Message-ID: <issues.opened-193742089-1481021896-sysbot+gh@w3.org>
tobie has just created a new issue for https://github.com/w3c/sensors:

== Don't allocate response objects to avoid triggering GC ==
On the list, @Maksims 
[writes](https://lists.w3.org/Archives/Public/public-device-apis/2016Nov/0027.html):

> **Garbage Collection** - one of the major bottlenecks and high 
consideration for real-time applications. If application is targeting 
60+ fps, it has to avoid any allocations and avoid calling any native 
JS methods that allocate response objects, for example 
getBoundingClientRect.
High GC loops do lead to periodical JS thread stalls, that can drop 
many frames, making 60fps unreachable.


Please view or discuss this issue at 
https://github.com/w3c/sensors/issues/153 using your GitHub account
Received on Tuesday, 6 December 2016 10:58:30 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 12:18:52 UTC