Hi all,

I do a lot of web development for work these days and I've had nothing but headaches with this build of Chromium. I've run into bugs with Arch build of Chromium that don't happen on a Debian Jessie build that I started using as a sanity check after running into weird issues with this build. I've also started using Chrome from AUR as the main browser because Chromium for Arch from extra is simply not reliable for me.

I've experienced the following:

1) Random loss of session cookies - for some reason, this build of Chromium has started losing session cookies. I'm not able to reproduce this with 100% repeatability, since they seem to happen randomly or get triggered in ways that I cannot track down, but session cookies just disappear after a certain time period. I've talked to people from Node.js on IRC, since I assumed it was a bug with NodeJS, but after one of the maintainers was not able to reproduce this, we started scrutinizing Arch build of Chromium and sure enough, it was happening to one of the core team members as well. This is not a Chromium "for Linux" issue since it does affect Chromium that Debian and Debian-based distros ship. This also doesn't affect Windows or macOS builds either. Only this build.

And this is also does not affect NodeJS only.... I've noticed my Youtube sessions lose cookies and require re-login.

2) Random crashes of tabs when opening links - this affected me few times and I could not explain it either. After looking at it more closely, it seems that Chromium for Arch has an issue with iframes and links under certain situations. It seems that someone else already reported this issue to Chromium team:

https://bugs.chromium.org/p/chromium/issues/detail?id=784492

Chromium core team members tracked it down to being an Arch-specific bug. I don't use this particular extension that triggered this report but I've noticed it with my install too. I'm sure other extensions trigger this bug as well. I have a around a dozen extensions and I'm not sure which one is responsible on my particular install. But in any case, this shouldn't be happening.

These issues are also not specific to 62.0.3202.94 (current build) since I've started noticing these weird issues for the past 30-60 days at the very least. I'm not sure what the root cause of this is but maybe one of the people more knowledgeable with this build can track it down.

Thanks!