I've noticed the same problem on the last couple stable channel releases (currently 69.0.3497.120) as well. Maybe significant is that I only see this on my enterprise enrolled device, and I think it only happens when the incognito window is in the work profile (incognito windows in other logged in profiles seem to work fine, and closing them does not crash the OS as far as I've seen).

Raising priority because reliably crashing the whole system seems a lot worse than a P3.

Including a feedback report from the consumer side: 
https://listnr.corp.google.com/product/208/report/85726169842?dateRange=All

I have not been yet able to reproduce the error.

Have you noticed any difference between when you open Chrome, then an incognito Window, or start directly in incognito mode?

Adding Arc as Android Apps are also terminated.

I'll try to do some more testing today, e.g. with direct incognito mode.

Note that while I also have arc enabled, I'm not sure the fact that the arc apps also die is much of a clue, since it looks like the whole OS essentially restarts (similar to going to chrome://inducebrowsercrashforrealz/), which kills all logged in sessions and running apps.

I'm running Canary on my Dell Chromebook 11 (codename: Wolf) and have not been able to reproduce this error on the recent Canary updates. 

I'll also try and reproduce later today and observe what I find. 

Reported again: crbug.com/896843

Issue 896843 has been merged into this issue.

I've verified that I can quite easily force a crash even if I close the main Chrome window and open only an incognito window. I've also tried with and without other profiles logged in, and with and without android (arc) apps running. Closing the incognito window reliably causes a crash in all situations (something like 6 in a row just now). The only requirement seems to be that the incognito window has navigated to a web site. When I opened an incognito window and immediately closed it, then it didn't crash.

I've also verified that it seems to only happen with my work profile on the device. I did a few tests switching over to my personal profile on the same device, but I wasn't able to get it to crash at all. I'll report back if I ever get it to crash, but considering how easy it was to crash the work profile, I would have expected at least one crash in the personal profile by now.

For the record, this is on a Pixelbook running current stable channel 69.0.3497.120 (and as previously mentioned, it was happening with at least one or two earlier stable releases as well, but I didn't make a note of those exact versions).

Did some testing. Opened Incognito and signed in to different Google Accounts, opening multiple tabs, etc. Still cannot reproduce. Version info below. 

Google Chrome	72.0.3582.0 (Official Build) canary (64-bit)
Revision	db5d271436f9329304e394c13ed3fb573588c2de-refs/branch-heads/3582@{#1}
Platform	11167.0.0 (Official Build) canary-channel wolf
Firmware Version	Google_Wolf.4389.24.62

Any ideas?

It looks like this might be the same as  Issue 890606 . Looking at some of my crash reports, they are all related to extensions code. I tried disabling all the extensions that I could, but incognito would still crash. However, I also have several enterprise policy enforced extensions which I can't disable (which probably explains why this only happens on my enterprise enrolled device), so I suspect it's one of those that's the problem, but since I can't control those, I'm not sure what else I can do to pinpoint the culprit.

mmoss@,

Could you please also check Canary? I've fixed a bug last week related to incognito/extensions/IME which could cause reference to freed memory and causing crash (crbug.com/856135). Now that scamdyn@ cannot produce it with Canary, maybe they are related.

I don't think I can easily test canary, since this is happening on my main work device, and I don't want to lose a bunch of data and configs (e.g. in ARC apps). I'll see if I can get another device to test with, but I'm OOO right now, so it will be at least a few days.

Could you point us at a few of your crash reports from chrome://crashes that might be related to this issue? 

Here are a few crash IDs from testing I was doing over the weekend. They all resolve to Magic Signature:
extensions::ChromeExtensionsBrowserClient::IsValidContext

aad33e3e43d77694
8e3c99dd3b922a8f
492543ebc70e86bd

Issue 899463 has been merged into this issue.

FYI, when testing this some more, I might have discovered a partial workaround for the crash. It seems that if the last tab closed in the incognito window is a New Tab Page, then Chrome doesn't crash. For instance, open an incognito window, then do some web searches or something. Now "ctrl+T" to open another tab in the incognito window, but don't do anything in that last tab. Go back to the tab(s) that you did your browsing in and close those, so that the only tab remaining is that new, "unused" tab. Then close that tab to close the incognito window. I've tried this several times now, and have yet to have it crash.

Any quick updates on this? I will keep monitoring this issue a little bit more. Thanks!

I'm working on it, but have not found any clue yet. If I don't find any reason by next week, I will just add more debug log.

Got it again on M72 dev (11210.0.0 (Official Build) dev-channel peppy). Sent logs with #wtlm-feedback and the bug number. If you need me to send anything over, let me know.

Sent feedback with the bug number and #wtlm-feedback-870838

I just reproduced on Canary. Sent feedback using Alt+Shift+i with the following tags in the first line to help find.
#870838 
#TFG

Sent at 12:20 PM CST

Sent feedback from M72 Peppy with the bug number in the first line

Here are  links to user feedback reports (with logs) that mention this bug in the description:

https://listnr.corp.google.com/report/85783903773 - M72 Dev
https://listnr.corp.google.com/report/85767728574 - M72 Dev
https://listnr.corp.google.com/report/85779941903 - M72 Canary
https://listnr.corp.google.com/report/85771160083 - M71 Beta
https://listnr.corp.google.com/report/85782419234 - M70
https://listnr.corp.google.com/report/85753765694 - M69

Just wanted to say that I am also seeing this behavior, for a few months now. I thought this was due to being on the dev channel, but this also happens on beta (Eve 71.0.3578.49/11151.29.0).

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f3432f4b0dde370f429a8a0c4d344b2c8d46766c

commit f3432f4b0dde370f429a8a0c4d344b2c8d46766c
Author: Ramin Halavati <rhalavati@chromium.org>
Date: Thu Nov 15 18:06:41 2018

Add fail safe mechanism to Extension Event Router.

To investigate a crash on ChromeOS, fail safe code and reporting are
added to EventRouter dispatcher and ChromeExtensionsBrowserClient.

Bug:  870838 
Change-Id: I8da1a56f80e247d68f26c8d8027f1eb36cea272f
Reviewed-on: https://chromium-review.googlesource.com/c/1335594
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#608434}
[modify] https://crrev.com/f3432f4b0dde370f429a8a0c4d344b2c8d46766c/chrome/browser/extensions/chrome_extensions_browser_client.cc
[modify] https://crrev.com/f3432f4b0dde370f429a8a0c4d344b2c8d46766c/extensions/browser/event_router.cc

@rhalavati, see issue 905896 for details on a feedback report I sent.

#33, Thank you, this crash points to a different code location, may shed some light.

I have not still found what is the root cause, but sent a patch (#32) to add fail safes to where the crash reports point to.

Once this goes into Canary, we can test if it has resolved the issue and I should get deeper into why it used to happen, or I was searching on a wrong lead.

I will ping here when it's in canary.

The fail-safe fix is in Canary. 

Could you please try to reproduce and if you succeed, send the crash id?

Issue 905896 has been merged into this issue.

Sorry for my delayed response, I will test the fix ASAP!

I have been able to reproduce the crash on 11277.0.0 (Chrome 72.0.3612.0, which includes the fix mentioned above). However chrome://crashes does not show anything after Chrome has restarted (says it has zero crashes). I have automatic crash reporting enabled - am I doing something wrong?

Strange! So you had a crash, and no crash report?
Are there a series of steps that result in the crash? I have not been able to reproduce it even once. :|

I have the same issue on my samsung chromebook plus.

rhalavati@: that's weird indeed. I have flashed this Chromebook using cros flash, maybe that can explain?

I got a repro on another Eve device, but this one is on the beta channel 72.0.3611.0. This time I got a proper crash report (ID 51362c44a3c689df) but I suppose it is not useful since it doesn't include your CL?

regarding repro steps: nothing 100% deterministic, but usually opening an incognito window, several tabs into it, going to some medium-weight sites (news sites/youtube) and closing all the tabs successively (I used ctrl+w for that) is usually enough to repro for me. Sometimes the crash won't occur though.

I also noted that the crash typically happens when the last tab takes some time to close (i.e. maybe garbage collection or something costly happens).

Finally, I have tried disabling all my extensions and could not repro so far. I need to test a bit longer to make sure that is actually the case, but if confirmed I should be able to bisect-enable my extensions in order to find which one triggers this.

#41, Yes, I need a crash with Canary 72.0.3612.0 or later. I don't know if flashing has effect on not sending the crash report or not, but if it happens again and doesn't send a report, then we should follow up that as well.

#42, The bisect approach would be great!

Has anyone experience a crash with Canary 72.0.3612.0 or later?

Version 70.0.3538.76 (Official Build) (32-bit)

NOTE: Issue doesn't occur when closing by either method with <5 minutes of use. Issue rarely occurs when closing with (CTRL+SHIFT+W).  Issue always occurs when closing with X.

#44, I am on dev 72.0.3609.3 at the moment, I will test out canary in a few minutes.

Adding to #46, so far no crashes yet. I will use this build for this week and I will let you know if I run into anything.

#44 just crashed with the system resuming at the login page. Just sent feedback with the bug number in the first line. Logs are attached as it exceeded he 3mb limit for the feedback report.

Deleted: debug-logs_20181126-121247.tgz 4.1 MB

debug-logs_20181126-121247.tgz 4.1 MB Download

#48, Could you please be more specific about crash conditions, was it after login (and not closing incognito windows)?
Isn't it more related to this  crbug.com/900548 

#49, had 4 tabs open (Discord, YouTube, Gmail, and Reddit) and closed them via ctrl+w which then crashed the system where the display went black and then came back at the login screen. I'll see if I can reproduce it again when I get the chance.

Was able to reproduce it, however it did not go to the sign in screen (what I saw may have been issue 894807, however I would have to find reliable ways to reproduce it.) 

Sent feedback with bug number in first line, logs are attached.

Deleted: debug-logs_20181127-133738.tgz 1.4 MB

debug-logs_20181127-133738.tgz 1.4 MB Download

Thank you, didn't it upload any crash report?

I didn't see any at the time of reporting, I'll check again to see if it ever did.

Thank you. Without the crash log I have no clue what to follow up.

I do see one crash from yesterday about an hour after the crash happened. The id is: 69be50b3e35f21d0

Digging around, I found another crash in /var/log/chrome/'Crash Reports'/uploads.cog

1543344232,69be50b3e35f21d0,Chrome
1543407462,9efac06197c61fc2,Chrome

Thanks a lot.
9efac06197c61fc2 shows a different stack trace and may be unrelated, but 69be50b3e35f21d0 seems to be a good sign and has moved the crash two functions higher in the stack.
Will update after I dig more.

BTW, it is still very helpful if we can have a [minimal] list of extensions that result in reproduction of this crash.

It seems that we have much less occurrences of the crash. I added another fail safe and let you know when it's in Canary.

BTW, has anyone experienced it when the incognito window has not been the only browser window? (I'm looking for race condition where browser is closed before some event is routed and that's why the crash happens).

This happens to me every time! Hope it gets resolved.

#59, such as having a normal browser window open as well as an incognito window? If so, that has happened a few times to me. 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/11590fa2e97bbb1e90aa3db36f60d76e85c8d551

commit 11590fa2e97bbb1e90aa3db36f60d76e85c8d551
Author: Ramin Halavati <rhalavati@chromium.org>
Date: Fri Nov 30 16:32:52 2018

Add more fail safes to Extension Event Router.

To investigate a crash on ChromeOS, fail safe code and reporting are
added to EventRouter dispatcher.

Bug:  870838 
Change-Id: I536a581c142d3b760f5a564507d4251b2b881c0e
Reviewed-on: https://chromium-review.googlesource.com/c/1356587
Reviewed-by: Ramin Halavati <rhalavati@chromium.org>
Reviewed-by: Devlin <rdevlin.cronin@chromium.org>
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Cr-Commit-Position: refs/heads/master@{#612668}
[modify] https://crrev.com/11590fa2e97bbb1e90aa3db36f60d76e85c8d551/extensions/browser/event_router.cc

This happens to me frequently as well on an asus C302C.  The last incognito tab to close crashes all the other chrome windows and other apps like mosh.

I am experiencing less occurrences of the crash, RE #59. 

I will keep trying to reproduce. I will post my updates as I go. 

Same for me on 11151.45.0 (Official Build) beta-channel swanky, however I do see it every now and again on M72-dev and M72-canary for peppy.

Thank you, the second fix is now in Canary 73.0.3627.0, could you please try that.
Having a crash report on this version would be very helpful.

I was able to reproduce it on M73 canary, I sent feedback around 7:30 with the bug number and "#wtlm-feedback". I attempted to attach the debug logs before but when I hit the "Choose file" the system crashed.

Deleted: debug-logs_20181203-073313.tgz 1.8 MB

debug-logs_20181203-073313.tgz 1.8 MB Download

Just saw that a new crash id popped up in chrome://crashes, the two that are there are:

1543501790,e122ab092633b7cc,Chrome
1543843245,1f9b9d65333eecee,Chrome

Thanks a lot,

e122ab092633b7cc (and 9efac06197c61fc2) belong to Canary 72.0.3609 which is prior to fail safes.

But 1f9b9d65333eecee belongs to 73.03628 which is after the 2nd patch. I am on it.

There is another thread on this. Merging with that one as it is more direct.

#70, issue 897946 is blocked to us outsiders, any chance we could get the the restricted view tag removed?

#71, I will follow up to remove the restriction.

This was happening constantly on my Acer 15 Chromebook. I figured it was a memory issue because I always have a lot of tabs open. Just bought a Pixelbook (i7 with 16GB Ram), and it happened this morning.

Version: Version 70.0.3538.110 (Official Build) (64-bit)

This typically happens when I have many tabs opened in a regular browser, then I open an incognito session, browse then close it. That's a strictly anecdotal observation though, so I figured this might be a good chance to run some controlled tests. Below is everything I've done so far:

At the moment, I have 18 tabs open (5 pinned tabs) all with different sites loaded.

1. Open a new incognito session (CTRL+Shift+N)
2. Close the session without navigating.

No crash.

Next:

1. Open a new incognito session (CTRL+Shift+N)
2. Navigate to Google.com but perform no search.
3. Close incognito

Repeated above steps a bunch of times and no crash.

Next:

1. Open a new incognito session (CTRL+Shift+N)
2. Navigate to Google.com
3. Search for phrase: hahahaha
3. Close incognito

I then searched one phrase (I've been testing with the phrase hahahaha which pulls up a more intensive Google search results page with images and video previews), closed the session and the crash occurred.

In Incognito, I went to a few other sites like Bing.com, PythonAnywhere.com, no issues, then went to yahoo.com (which I'll note is a much heavier page than the others) and it happened again upon closing Incognito.

Next, testing whether pinned tabs are the problem:

1. I unpinned the 5 pinned tabs
2. Opened incognito session (CTRL+Shift+N).
3. Went to Google
4. Closed Incognito

No crash.

Next:

1. I opened incognito session (CTRL+Shift+N)
2. Went to Google
3. Searched hahahaha

No crash. Repeated 1 more time without a crash then the next attempt crashed. Repinned the 5 tabs and it happens pretty much every time I go to Google and search a phrase.

Next, testing if it is just the quantity of tabs causing the problem:

Closed a bunch of tabs. Now just have 5 pinned tabs and 2 regular tabs.

1. Open Icognito (CTRL+Shift+N)
2. Navigate to Google
3. Search phrase (phrase: hahahaha)
4. Close Incognito

Crashed.

Did multiple repeats of previous tests above with only these 7 tabs and all results are basically the same.

I'm now going to test if this is more caused by page size. I've profiled 10 relatively popular websites based on their load size from Chrome Dev Tools and their memory usage from Chrome Task manager. I then ran 10 tests against each site and counted the number of crashes that happened out of those 10 tests. My spreadsheet can be seen here: https://docs.google.com/spreadsheets/d/1DMzrjdtNgGEW0ykyEbg-G9THog-qPVzo-CYlUxGpZzc/edit?usp=sharing

Test methodology: For all sites, except the Google test where I search for my phrase, I simply went to the homepage, waited for everything to appear loaded, I then closed the page using the X in the incognito session. I only had one tab open at any time during the test, and I always launched the Incognito session using CTRL+Shift+N.

I was hoping for a really strong correlation, but as you can see, some sites just don't seem to be affected. For nothing else, at least this provides some sites that exhibit some consistency in the crashes which will hopefully help with future testing. I hope someone else can reproduce my results and I hope this information helps track down the problem. Have a great weekend everyone.

An addendum to my above tests: I got a bit sloppy in my step documentation in the middle part.

All crashes happened upon closing the incognito session.

My notes above might give the impression that some crashes occurred when performing a Google search, which was not the case. All crashes happened when closing the incognito session.

kristoferphelps@,

Thank you very much for extensive testing, could you please do it with latest Canary and send crash ids as well?

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/fe2afba1ac90f7a0a8784bb8a4dec7c4831aca98

commit fe2afba1ac90f7a0a8784bb8a4dec7c4831aca98
Author: Ramin Halavati <rhalavati@chromium.org>
Date: Mon Dec 10 06:52:54 2018

Add one more fail safe to Extension Event Router.

To investigate a crash on ChromeOS, fail safe code and reporting are
added to EventRouter dispatcher.

Bug:  870838 
Change-Id: Ibb2ce7b593c3a7c6b6c2f2ee61c150d37021335e
Reviewed-on: https://chromium-review.googlesource.com/c/1366329
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Reviewed-by: Ramin Halavati <rhalavati@chromium.org>
Commit-Queue: Ramin Halavati <rhalavati@chromium.org>
Cr-Commit-Position: refs/heads/master@{#615061}
[modify] https://crrev.com/fe2afba1ac90f7a0a8784bb8a4dec7c4831aca98/extensions/browser/event_router.cc

kristopherphelps@, have you observed this since moving to the latest Canary build? If so, could you provide any crash ids from chrome://crashes ?

Hey there,

Sorry for the delay. Unfortunately, I use these computers for my business, so switching to developer mode to switch between builds is a no-go for me.

Ridiculous that this hasn't been fixed yet

Yeah, can someone *please* look into this? I got my Pixelbook last month during the sale and this happens almost everytime I try to use Incognito mode. Was there on the Beta channel and Stable channel.

Do you have any new crash report ids related to this issue?

I have just been testing this issue on 72.0.3626.49 (64 bit), on a Toshiba Chromebook 2. I can confirm that is is still occurring exactly as documented kristofe. Unfortunately, despite having crash reporting enabled I am not seeing any crash reports in chrome://crashes/ after the issue occurs. I am at a loss as to how I can report further diagnostics so am welcome to suggestions.

Yep, same thing here. I have crash reporting enabled too, but nothing appears in chrome://crashes after the crash. However, it does seem to crash most often after doing a relatively resource-intensive task like watching a YouTube video or browsing Reddit. Also, it won't usually crash if you just use Incognito and instantly close it. It happens after using Incognito for at least a minute or two.

I'm on a Pixelbook running stable channel 71.0.3578.98 and I'm seeing a crash report in chrome://crashes when my Incognito session crashes. The latest crash ID is 8151d215f84d5738

The latest fail safe for this is added to Canary 73.0.3637.0, and it's still not in stable branches.
Can you test with that?

Updated to M73 dev and this is now effecting the browser as well, but crashes when you close a tab. I know this is not the same issue, but it has the same behavior as described in previous comments. Here are the bug reports from today:

a32038f44da039b1
29f41641f6fd4783
98660633ea4ffb79
754c12a83d880c54
f17f896fcdff8a7a
5ee87b784787a1a0
ba8194088c39c47c

Just been testing again on 73.0.3669.0 64-bit and can confirm it is still happening. 

Test was as follows (going from immediately after startup with all apps and tabs closed):
1. Open a tab and go to developers.google.com
2. Open an Incognito window and go to www.facebook.com (just a visit to the home page, did not log in).
3. Close the Incognito window and the OS crashes.

I am now seeing crash ID's in chrome://crashes from January 11th testing but not yet for today's crash. (Is there a delay in these showing up?)
ID's from 11th Jan are:
56b8f3b70d329416
84b7f916259fb67b
b1ee2717dbc8f1fa
c7b8e147456b3ded

I now do have a crash report from this evening: 2cc2a97ab3c68aac

Further testing suggests this problem only occurs on 73.0.3669.0 when certain extensions are enabled.(This is on a Toshiba Chromebook 2 - Google_Swanky.5216.238.150.) I started by disabling all extensions and could not reproduce. I then set about enabling extensions one at a time. The problem only manifested when two of my extensions were enabled; Ghostery and TunnelBear. Notably, both are enabled in Incognito mode but enabling other extensions in Incognito mode did not lead the problem to occur.

One more thing; I just disabled Ghostery in Incognito mode and can no longer reproduce the problem.

willlandrieu@, j.godsland@: Thanks a ton for helping out with this! This is very useful information.

rhalavati@: It seems that all crashes in comment #88 and some of those in comment #87 are extension-related. Consider splitting that out into a separate bug and passing to the extensions team. The rest looks like we crash when we're trying to focus the window that is being closed.

Ok, I disabled one of my extensions (AdBlock) in incognito and can confirm as well that I am no longer able to reproduce it.

If it is an extensions issue, can someone send this to the extensions team?

Just crashed on M72 Nautilus, no crash data was there. I'll try disabling extensions tomorrow and see if that fixes things.

Our main suspicion has been on the extensions and the previous fail safes were all on extensions::EventRouter and so is crbug/897946.

One major problem in debugging the issue was that neither I nor the owner of crbug/897946 could not reproduce it. crbug/917619 suggests one extension and I am following that up. If you can suggest your AdBlocker extension as one reliable source of crash it would be very helpful as well.

+lazyboy@ who is working on crbug/897946


#88: I checked your crash ids and they all belong to 72.0.3626.49.

#87:
Only 754c12a83d880c54 belongs to the function that we were monitoring before, the reset are on:
views::FocusSearch::FindNextFocusableViewImpl

#86
Is this still the latest fail-safe?

#94
I am not sure if this could potentially have anything to do with it, but I have uBlock Origin enabled in Incognito. It's the only extension I have enabled in Incognito, otherwise I have many other extensions I use in the normal browser. 

I will continue testing today, I haven't been active towards this bug but I'm planning to continue further testing and suggestions. 

Addition to #96
Also, I think when I first reported this bug I did have ZenMate VPN extension enabled in Incognito. 

#95 Correct, as I said in comment #88 they were from 11th January, i.e. related to comment #83. Ignore if no longer relevant. Comment #89 has a crash report from 73.0.3669.0 which is also the build I was testing plugins on.

I can also confirm that the problem no longer manifests on Stable (71.0.3578.98), once the offending extensions are disabled in Incognito. To be precise, this was tested with the "Ghostery" extension enabled but not "Allow In Incognito" set to off.

I can confirm that disabling extensions has fixed the issue, however has not resolved the new M73 bug with it happening in non-incognito windows. I created Issue 922937 which does have the Restricted View tag on it since it has crash logs.

Adding to #97, I also have been using a VPN (Windscribe) whic has the VPN service itself and a copy of uBlock origin.

Thank you. I tried AdBlock, Ghostery, uBlock, and ZenMate VPN, but could not reproduce it.

But I could FINALLY see it using PIA (mentioned in another bug). I have removed the restricted-view on crbug/897946, so please add your next comments/findings to that.

OMG it's been more than 4 months and it's not fixed yet :(

I noticed that this is marked as closed Dec 3. Is there a solution?

Mine still crashes. Reproducible 100% of the time:
- Chrome Version 71.0.3578.127 (Official Build) (64-bit)
- Acer Cromebook C720 - 4GB Ram
- Incognito mode
- Example: Playing any YouTube video
- Hit the X in the top right to close just the one window:
Crashes all windows