The crash linked here appears to be unrelated to the described issue -- it's an ANR in com.android.vending/com.google.android.finsky.scheduler.AlarmEngineService.

Then I suppose this type of crash is not logged at all. Or is there another location where I can look for crash logs?

Tested with 67.0.3375.0 on Cave - UI becomes unresponsive for several seconds and recovers.
Tested with 67.0.3366.3 on Eve - Works fine.

Going to give it a shot with the latest canary on Cave (waiting for update now) If that doesn't work I'll reimage my eve to the specific version (trying to avoid that as I have other stuff being tested on that device right now)

Is there anything here that requires the bug to remain restricted? I don't see anything.

67.0.3390.0 on Cave is the same as 3375 -- Unresponsive then recovers.

+vapier@ for wicked good unarchiver.

At a minimum, selecting a large number of files in an archive shouldn't stall the system like this.

I'll keep hunting for a repro of the crash

Allowing triage team to prioritize and assign owner.

I suspect it is a browser hang than a crash. UI thread seems really busy with the select-all operation. If chrome fails to respond to session_manager's liveness check ping, it would get killed.

Could we file a feedback? We can look at syslog part of the report and looking for "Browser hang detected!". That line should be present when chrome is killed due to failed liveness check ping.

Please reproduce again and send feedback with Alt+Shift+I so we get the syslog in the reports.

i don't think WGU is really a factor here.  the Files App/API/structure should take care of staying interactive regardless of the requests.

I can't repro on 67.0.3383.0 on Eve either. The UI stalls for a few seconds but recovers. 

I think xiyuan@ is right; some operation is blocking the UI and in some circumstances leads to the browser getting killed by hang detection.

pashkov@ can you repro the crash and then file a feelback report with alt+shift+i? That should allow us to see more detailed logs that will let us confirm or deny the suspicion.

I'm also going to unrestrict this since I don't see anything confidential here.

pashkov@ - can you repro and file a feedback report so we can further investigate? Thanks :)

Sorry, I cannot reproduce it either anymore.