Status Update
Comments
ma...@gmail.com <ma...@gmail.com> #2
I notice the same issue and LogCat shows the following message:
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
lg...@chromium.org <lg...@chromium.org> #3
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
ma...@chromium.org <ma...@chromium.org> #4
me as well....
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
ma...@gmail.com <ma...@gmail.com> #5
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
ma...@gmail.com <ma...@gmail.com> #6
Having the same issue:
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
ka...@google.com <ka...@google.com> #7
same
ma...@gmail.com <ma...@gmail.com> #8
SAME ! - Google can't do sth working in 100 percent?
da...@gmail.com <da...@gmail.com> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
Description
Steps to reproduce the problem
I am not entirely sure, and cannot create an actual reproduction scenario. But it DOES happen with the following code: .container { width: 100%; height: 100%; display: grid; -ms-overflow-style: none; scrollbar-width: none; background-color: white;
&::-webkit-scrollbar { display: none; }
.header { position: fixed; z-index: 3; right: 0; width: calc(100% - var(--border-width)*2); left: var(--border-width); border-top-left-radius: calc(var(--wrapper-border-radius)*0.5); border-top-right-radius: calc(var(--wrapper-border-radius)*0.5); overflow: hidden; }
.mediaContainer { position: sticky; width: 100%; height: 100%; display: flex; align-items: center; justify-content: center; top: 0; z-index: 1;
}
.contentContainer { position: relative; width: 100%; height: 100%; z-index: 2; }
&.fullWidthContainer { position: relative; width: 100%; height: 100%; display: flex; justify-content: center; align-items: center;
} }
@container (width > 975px) { .container {
} }
.container { overflow-y: auto;
&.stickyHeading { overflow-y: unset;
} }
@media (min-width: 976px) { .container { overflow-y: unset;
} }
@container (width < 976px) { .container { grid-template-columns: 100%; height: 100%;
} }
And does NOT happen with the following code: .container { width: 100%; height: 100%; display: grid; -ms-overflow-style: none; scrollbar-width: none; background-color: white;
&::-webkit-scrollbar { display: none; }
.header { position: fixed; z-index: 3; right: 0; width: calc(100% - var(--border-width)*2); left: var(--border-width); border-top-left-radius: calc(var(--wrapper-border-radius)*0.5); border-top-right-radius: calc(var(--wrapper-border-radius)*0.5); overflow: hidden; }
.mediaContainer { position: sticky; width: 100%; height: 100%; display: flex; align-items: center; justify-content: center; top: 0; z-index: 1;
}
.contentContainer { position: relative; width: 100%; height: 100%; z-index: 2;
Problem Description
once I make the viewport smaller than 975px chrome segfaults
Summary
Segfault (code 11) in Chromium due to conflicting scrollbar styles when resizing the container.
Custom Questions
Crashed report ID:
b65e7a9c-ea2a-4c6e-a1ac-caf7ab825ada
How much crashed?
Just one tab
Is it a problem with a plugin?
No - It's the browser itself
Additional Data
Category: Crashes
Chrome Channel: Stable
Regression: No