RE: W3C Navigation Error Logging - log when UA crash/freeze? from Aaron Heady (BING AVAILABILITY) on 2014-10-21 (public-web-perf@w3.org from October 2014)

From: Aaron Heady (BING AVAILABILITY) <aheady@microsoft.com>
Date: Tue, 21 Oct 2014 20:24:57 +0000
To: "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <28032ce1578e42b88b9f121b0698e49d@BLUPR03MB133.namprd03.prod.outlook.com>

Any thoughts on this?

-----Original Message-----
From: Aaron Heady (BING AVAILABILITY) 
Sent: Tuesday, October 14, 2014 1:38 PM
To: 'public-web-perf@w3.org'
Subject: W3C Navigation Error Logging - log when UA crash/freeze?

Curious about a possible addition to the scope of what logging covers. Does anything in the spec capture when a page load crashes the browser tab or causes it to be unresponsive? We ran into an obscure situation that we hadn’t tested for and managed to get a UA to crash, looks like it was related to a style recalculation. 

Could we/should we log an error entry on the page/domain when the UA crashes/freezes, so we can see at scale that something we released is increased the crash/freeze rate for the global user base?

Thoughts?

Aaron

Received on Tuesday, 21 October 2014 20:26:09 UTC