Re: 答复: W3C Navigation Error Logging - log when UA crash/freeze?

This would be really fantastic to have. At Facebook, we once noticed an
increased rate of employees reporting Chrome crashes. We were able to track
this down to the rollout of a new version of SPDY -- it was something that
affected all FB users. When we talked to the chrome team, they were able to
see an obvious graph of the increased crash rate. It took us a few weeks to
figure this out (it took a long time to get enough employee reports to
investigate, plus we had to guess the cause).

If we got logs of UA crashes, we would have been able to figure this out
much more quickly.

The alternate strategy here is for UAs to use their internal reporting
mechanisms and expose them to developers. One advantage of this method is
that it might be possible to give some sites more data (eg, sharing stack
traces).

-b

On Wed, Oct 22, 2014 at 8:28 AM, Ilya Grigorik <igrigorik@google.com> wrote:

> Aaron, Liang, do you have any existing data on size of the problem?
> Examples of how and where it helped?
>
> I figure every browser maintains some internal tracking for crash counts
> (we do with Chrome), but it's not clear to me that this data is actionable
> for the developer. Many crashes have nothing to do with site's application
> code, and often times its hard to figure out who's at fault (site vs.
> browser bug, etc).
>
> ig
>
> On Wed, Oct 22, 2014 at 1:58 AM, Liang,Tao <liangtao01@baidu.com> wrote:
>
>> I agree with Aaron Heady's advice. In fact, it's useful to see the
>> release's effect on crash for global user base and to supply a way to
>> improve the product.
>> But does Navigation have an opportunity to logging Crash / Breeze ?
>>
>>
>> -----邮件原件-----
>> 发件人: Aaron Heady (BING AVAILABILITY) [mailto:aheady@microsoft.com]
>> 发送时间: 2014年10月22日 4:25
>> 收件人: public-web-perf@w3.org
>> 主题: RE: W3C Navigation Error Logging - log when UA crash/freeze?
>>
>> 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
>>
>
>