I suspect the 12 screen shots of each tab in window 1 caused the failure of my first attempt to send; if you want to see them, let me know. The whole totaled only 2.3 MB.

Unable to reproduce the issue on mac 10.12.6 using reported chromium and chrome version #67.0.3396.87 and latest chromium version #69.0.3466.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened Chromium.
2. Opened 12-13 urls provided in the attachment "Chromium Tabs.rtf" and observed that all the tabs displayed remote content as expected.

whldorsey@ - Could you please check the issue on latest chromium version #69.0.3466.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Also please check the attached screen cast and please let us know if anything missed from our end.

Thanks...!!

Deleted: 854625.mp4 2.4 MB

	854625.mp4 2.4 MB View Download

Thanks for your response.

I am not yet able to download the version you list (see attachment) — I do
not know any other path to get to the new version before Woolsyss makes it
available.
But I will check back until I can then get back to you.

Meanwhile, how can I first delete my current profile in Chromium, then
start a new one? (I do not remember ever doing that.) I want to try it with
the one I have installed.

ALSO, in your email the attachment is listed but not apparently actually
attached.

Thank you for providing more feedback. Adding the requester to the cc list.

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

whldorsey@ - Thanks for your comments...!!

The latest chromium versions for OS-mac can be downloaded from below url:
https://chromium.woolyss.com/download/#mac.

For creating a new profile no need to delete the existing one. Please follow the below steps to create a fresh profile:
1. Click on the "avatar icon" on the top right corner and click on the "manage people".
2. Click on "add person" and click on any icon and then click on "add" button. 
3. A fresh profile gets created.

Please check the attached screen cast and please check the issue on latest chromium version #69.0.3468.0 by creating a new profile without any apps and extensions.

Thanks...!!

OK I downloaded and installed *Chromium 69.0.3474.0 (Developer Build)
(64-bit)*
I *went through the steps to create a new profile*, going from my GMail
photo to Person 1, noe with no picture but my name
I closed the windows that open because that group of tabs is mainly what I
use Chromium for, opening a blank page
I got the *same result*:
This site can’t be reached

*https://tvlistings.zap2it.com/?aid=gapzap
<https://tvlistings.zap2it.com/?aid=gapzap>* is unreachable.
ERR_ADDRESS_UNREACHABLE

(Finally, again, the screencast mentioned in the first response was not
attached.)

Thank you for providing more feedback. Adding the requester to the cc list.

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

As per comment #3 and #6, unable to reproduce the issue from TE-end. Hence, removing the Needs-Bisect label and requesting someone from Blink team to please have a look into the issue.

Thanks...!!

As per comment #9, as this issue is not reproducible at TE end, adding 'TE-NeedsTriageHelp' label and requesting the appropriate team to look into the issue and help in further triaging.

Thanks..

Thanks for your report. It sounds like your network configuration is screwed up in some way. Marking for network triage.

Hey whldorsey,
I think we need a bit more information to help here. Can you please reproduce this problem by following the instructions here and attaching a net-export dump?
https://dev.chromium.org/for-testers/providing-network-details

Thanks for your attention.
just in case you might be working from a misunderstanding, I just want to
point out that all of the sites open in every other browser — Safari,
Chrome, Firefox, Sea Monkey, Opera, Tor (all are up=to-date).

Might an Apple Log file or other system-generated report be helpful? Oh, I
see the next email, asking for a network dump; I'll try to get that and
send it.

​
 chrome-net-export-log.json
<https://drive.google.com/file/d/1YSpaQyJOEIl0eS9WpJ1u1DTm05Wv93Yo/view?usp=drive_web>
​

[whldorsey]:  Sorry for the slow response.  For some reason, our Needs-Feedback tool didn't detect that you'd given us feedback.

I assume you're still having the issue.  It looks like network connection attempts are failing with ERR_ADDRESS_UNREACHABLE.  I only see connections to IPv6 addresses, so I suppose the issue could be that you're on an IPv6 intolerant network, and we don't detect it.

Could you open up a terminal window, and type:

ping 2607:f8b0:4002:c00::8a

And see if you can connect to it?

1. Here is the result:

williamrseysPro:~ Dorse$ ping 2607:f8b0:4002:c00::8a

ping: cannot resolve 2607:f8b0:4002:c00::8a: Unknown host

2. What's confounding is that there were no changes between the last time
it worked and the beginning of it not working.

3. Your email reminded me of a time when I had a problem because one app
set up a proxy connection that interfered with other apps if they were run,
so I just checked out the proxy list — nothing is turned on, as is normally
the case — and am attaching a screen shot

4. Once i the last few days I opened Chromium and one of those pages
actually did load. I immediately checked the others and when I got back to
the one that had worked, it was again not connecting. I don't know if
that's helpful or not.

I assume pinging 2001:4860:4860::8888 also gives you unknown host?  For our IPv6 reachability test, we open a UDP socket to that address, and make sure that it both succeeds, and the local end of that socket looks reasonable.  It seems weird that you'd be getting "unknown host" from pings in the case where we can actually create an IPv6 socket to that host.

We could consider mitigations on our end (Like falling back to IPv4 in response to ERR_ADDRESS_UNREACHABLE), but given that no one else seems to be running into this problem, I'm reluctant to make changes in Chrome as a workaround.

I pasted in the entire Terminal response, which ended with "Unknown host."

Is it possible that this problem is a result of Chromium not being "signed"
and Apple (I'm on a desktop Mac Pro) or AT&T (my provider) having made a
change that now stops whatever behind the scenes handshaking is expected?

You could try Chrome instead, experimentally, but that doesn't sound likely to me.

Note that what's failing isn't handshaking - we create a socket (Without connecting it) to an IPv6 host, and the OS claims that works fine, which indicates you have IPv6 connectivity.  Then we try and connect to an IPv6 host, and things fail with no route to host.  The fact that ping fails with unknown host (Instead of no route to host) seems to indicate that either some subset of IPv6 host names are recognized as known hosts, or we're getting a different view of the world than the ping command.

Could you ping 2001:4860:4860::8888 as well, to see which it is?

I switched to Chrome to keep up with those sites I'd been using Chromium
for. (No problems.) When I went to Chromium earlier today the
non-dynamic(?) pages still are holding onto their cache images, for the
most part.

Here's the result of the second ping:

williamrseysPro:~ Dorse$ ping 2001:4860:4860::8888

ping: cannot resolve 2001:4860:4860::8888: Unknown host

(Removing Needs-Feedback label since it doesn't look like we're waiting on a NetLog or anything.)

Adding the connectivity and DNS labels - issue here seems to definitely be that the network doesn't support IPv6, but that we think it does.  Wonder if we should try to fall back to IPv4 if we get ERR_ADDRESS_UNREACHABLE for IPv6.  We have other filed bugs about being too aggressive in the opposite direction - thinking we don't have IPv6 support when we actually do (And in fact have only IPv6 support).  Not sure there's any easy fix that addresses both issues, though.

Bug reports for incorrectly IPv6 seem a lot more common than reports for using it when we shouldn't, so the other problem seems to be a bit more common.