Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Chromium crashes on "Stop using invalid certificate" on N5 #233
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Apr 14, 2016
Contributor
Does this still crash for you with the latest update? There's a new Chromium build. I expect that the problem is still unresolved but it might be fixed in the next major version. I think it must be an upstream issue.
|
Does this still crash for you with the latest update? There's a new Chromium build. I expect that the problem is still unresolved but it might be fixed in the next major version. I think it must be an upstream issue. |
thestinger
added
the
upstream
label
Apr 14, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
reenz0h
Apr 14, 2016
I'll try to test it once again. Also as thestinger suggested on IRC, will try to install the app on stock (under emulator).
reenz0h
commented
Apr 14, 2016
•
|
I'll try to test it once again. Also as thestinger suggested on IRC, will try to install the app on stock (under emulator). |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
reenz0h
commented
Apr 14, 2016
|
Crash still occurs - tested on build MMB29X.2016.04.10.03.35.03 |
thestinger
added
Type: bug
upstream-app
and removed
upstream
labels
May 20, 2016
thestinger
added this to the Release milestone
Jul 12, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Jul 23, 2016
Contributor
This is caused by not using the Chromium linker due to #202. I don't want to track upstream Chromium issues here. The only approach that will be taken here is fixing compatibility with the usual custom linker.
|
This is caused by not using the Chromium linker due to #202. I don't want to track upstream Chromium issues here. The only approach that will be taken here is fixing compatibility with the usual custom linker. |
thestinger
closed this
Jul 23, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Jul 23, 2016
Contributor
Here's an upstream issue: https://bugs.chromium.org/p/chromium/issues/detail?id=630863/. It's the same problem as the other case.
|
Here's an upstream issue: https://bugs.chromium.org/p/chromium/issues/detail?id=630863/. It's the same problem as the other case. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment Hide comment
thestinger
Jul 24, 2016
Contributor
Since #202 has been fixed, this problem will be avoided by using the Chromium linker again. The upstream bug is still present and I'd like to disable the Chromium linker again once it's resolved though.
|
Since #202 has been fixed, this problem will be avoided by using the Chromium linker again. The upstream bug is still present and I'd like to disable the Chromium linker again once it's resolved though. |
reenz0h commentedApr 9, 2016
I'm not sure if it's somewhat related to this: #229 but I've noticed that Chromium crashes when "Stop using invalid certificate" is chosen from certificate/connection details.
Testing procedure:
Phone model: Nexus 5
Build number: MMB29X.2016.04.05.04.42.49
Security level set: middle (no additional sec features turned on)
Language: English
Logcat: