What desktop environment / window manager are you using?

no desktop environment, i3-gaps https://github.com/Airblader/i3

If Chrome is crashing, can you provide a crash id?  See http://dev.chromium.org/for-testers/bug-reporting-guidelines/reporting-crash-bug (specifically the link to enabling crash reporting and getting a crash id).  That will guide us much more quickly to the problematic code.

[Tentative label with Internals>Network to get on net triager's radar; if this is a UI problem, the label should probably be changed.]

I'm trying to get you the crash data, but I can't find how to turn on crash reports.

Following these instructions:
https://support.google.com/chrome/answer/96817
On your computer, open Chrome.
At the top right, click More More and then Settings.
At the bottom, click Show advanced settings.
To turn this setting on or off, under "Privacy," select the checkbox Automatically send usage statistics and crash reports to Google.

However, the setting isn't listed under privacy settings. Additionally, ctrl-f for "crash" doesn't find anything. Is there an alternate way to get crash data?

chrome://crashes just says reporting is turned off. I'd prefer not to install the debugging packages.

Are you using Chrome installed from Google or a Chrome that's installed with your Linux distribution from a package?  Sometimes the distribution maintainers play with Chrome.  (Regardless, you shouldn't need to install the debug version of the package.)

Having said that, it seems really strange to me that that setting isn't listed under privacy settings.  For me it's the 7th one down, just above "Send a 'Do Not Track' request with your browsing traffic" and just below "Use a web service to help resolve spelling errors".  Do you have those options?

Probably through apt-get install chromium? 

I have these options:

Privacy:
Use a web service to help resolve navigation errors
Use a prediction service to help complete searches and URLs typed in the address bar
Use a prediction service to load pages more quickly
Automatically report details of possible security incidents to Google
Protect you and your device from dangerous sites
Use a web service to help resolve spelling errors
Send a "Do Not Track" request with your browsing traffic

As you can see it's not in between those two

Actually, now that I think about it, it makes sense that option isn't there.  Sorry for sending you on a wild goose chase.  The basic issue is that I believe the Linux distributions compile packages from the Chromium repository; they don't take the binary from Google.  As a result, if it *did* upload a crash report, we wouldn't know what to do with it, because it's not our binary--we wouldn't have symbols, we wouldn't know how it was compiled, and the bug might be in distribution added code rather than ours.  Which I suspect means we can't do anything with this bug :-J.

Pawel, I think of you as being fairly expert on Chromium<->Linux distribution interactions; does the above analysis sound right to you?

Quick update: I just accidentally hit ctrl-s (save) and the browser crashed so it looks like any/every file dialog is doing it.

Is there a more appropriate place to send this bug report?

The bug report system of the linux distro that you're using?

Also please try to follow https://chromium.googlesource.com/chromium/src/+/master/docs/linux_debugging.md and get a stack trace.

Depending on the distro, you'd need debugging symbols - see e.g. https://wiki.debian.org/Chromium/Debugging and https://wiki.ubuntu.com/Chromium/Debugging .

Thank you for providing more feedback. Adding requester "juliatuttle@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

This appears to still need feedback in the form of a crash ID or a stack trace.

rch@ Crash reporting is disabled for zakstrassberg@ because he's using Chromium.

Maybe if OP tries this on Google Chrome instead, we can get a crash ID (or see if it repros at all)?

 zakstrassberg: If you're using a Chromium distro rather than Google Chrome we can't help you--all of our debugging tools are oriented towards Google Chrome.  Could you try and reproduce this problem in Chrome?  

(If we don't hear from you weren't going to have to close this bug.)

Closing for lack of feedback.