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

Thanks for looking into this. After a cursory glance at the comments on the Chromium thread, it doesn't seem to address the case where you have more than one reading per frame, what happens when these objects are kept around longer than a frame (Hannes' comment about GC easily taking "several milliseconds" in certain cases is particularly worrying), or whether that has an impact in a larger application settings (which is what the OP was concerned about).

It would also be important to get feedback from other implementors on this topic (which might have different GC strategies).

-- 
GitHub Notification of comment by tobie
Please view or discuss this issue at https://github.com/w3c/sensors/issues/153#issuecomment-287853468 using your GitHub account

Received on Monday, 20 March 2017 18:25:50 UTC