Shruthi, are we seeing a spike in crashes on Canary? Do we have any leads yet?

rtenneti@ is the stability sheriff today, and manoranjanr@ is the crash triage sheriff. They should be able to help!

gab@, just to make sure, are you still seeing this on the latest canary (51.0.2689.0)?

We are not seeing any Windows Extension crash spike for 51.0.2686.0 as well as on Latest Canary#51.0.2689.0.

https://crash.corp.google.com/browse?q=product.name%3D%27Chrome%27%20AND%20product.version%3D%2751.0.2686.0%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27extension%27&ignore_case=false&enable_rewrite=true&omit_field_name=&omit_field_value=&omit_field_opt=%3D#-samplereports:5,magicsignature:20

Just wanted to know, if no crash is registered under chrome://crashes would it really shows-up in crash server (go/chromecrash or any crash server data base)?

Thank you!

@#3: yes.
@#4: exactly, I think this may be missing our radar. I get desktop notifications bubbles for each extension saying it has crashed, but nothing in chrome://crashes.

Rechecked this on chrome version 51.0.2686.0, 51.0.2687.0 and Canary version 51.0.2695.1 and Asan 51.0.2695.2 on Windows 8.1. 

Added around 10 to 15 Extensions. No extensions crashes.
Closed and relaunched chrome. None of the installed extensions crashed.
Restarted system and launched chrome. None of the extensions crashed.

@gab: Request you to please recheck again. Also can you please let us know the list of extensions installed so that we can try with the same.

Removing bisect label, please add if required again. 

The problem is not so much that extensions crashed (the all extensions crashing problem appears to have gone away for now), but that nothing is shown in chrome://crashes.

I just got another extension crash (this time "Application Launcher for Drive" and "Inbox by Gmail" -- other extensions stayed up this time) on startup, but still nothing in chrome://crashes.

Are extensions crashes reported through another channel?

+amineer for stability in general. Alex, is this a known issue that extension crashes don't provide crash IDs?

Not something I'm aware of nor something that should occur.  Over to the first person I could find listed for the Chrome extensions team to review and route, as adding to component Platform > Extensions hasn't gotten this a better owner.

I just tested on windows with current stable build (51.0.2704.19) and recent canary (52.0.2717.0). I tried generating crashes in 2 ways:

a) by killing the process for an extension using task manager
b) by entering about:crash into the omnibox for a tab that had been navigated to chrome-extension:// URL. 

The behavior for canary and stable was the same - for (a), I didn't get any entries in about:crashes, but for (b) I did. (I also tested that this is the same behavior for a regular renderer navigated to a https web page)

Is it expected that killing the process using task manager doesn't generate a crash report?

gab, is it possible that something like misbehaving antivirus was causing the extension processes to be killed in a way similar to task manager that doesn't lead to crash reporting? 

Oops, I just realized that 51.0.2704.19 is dev channel, not stable. 

FYI, I just tried again with 50.0.2661.87 and got same results as I mentioned previously in comment 11. 

@#11: Yes it's possible, this is Windows corp after-all so anything is possible ;-). The browser process and non-extension renderers don't crash though so it is extension specific and it is hitting our blind spot. Any ideas on figuring out what is causing the crashes?

I've asked around and so far no one has heard of similar recent bug reports. 

One theory for why nothing was listed in about:crashes - someone thought that the only crashes listed there are ones that have been successfully uploaded to the crash server, so if all extensions crashed and one of the crashed ones was BeyondCorp (that provides proxy settings for corp-managed accounts), maybe network access wasn't working and that prevented the crash reports from being uploaded? Have you happened to check about:crashes again since things started working again?

If the processes died in a way that didn't leave any crash dumps, and the problem isn't reproducible, I'm not sure what more we can do. 

I'm happy to WontFix this per lack of repro (hasn't happened again in a little while for me..). But if you want to leave some steps to try if it does happen again one day, I'll be happy to run through them then.

Hmm, I guess you could look in AppData\Local\Google\Chrome\User Data\Crashpad\reports to see if there are any new .dmp files there. 

Ok will do and re-open if I find something (or if it happens again that I see crashes without data)