New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 118706 link

Starred by 80 users

Issue metadata

Status: Fixed
Owner:
OOO through 11-26
Closed: Apr 2012
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug

Restricted
  • Only users with EditIssue permission may comment.



Sign in to add a comment

HTTPS/Certificate websites always have "Invalid Server Certificate" Error

Reported by b...@kulbertis.org, Mar 16 2012

Issue description

Chrome Version       : 19.0.1068.1 (Official Build 126852) dev-m
URLs (if applicable) : https://google.com/
https://facebook.com/
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
     Safari 5: Untested
  Firefox 4.x: Ok
       IE 7/8/9: Ok

What steps will reproduce the problem?
1. Request any webpage using https

What is the expected result?
The browser would accept the certificate because it actually is valid and the page would load normally.

What happens instead?
Chrome displays an error claiming the website's certificate in invalid (see attached screenshot)

Please provide any additional information below. Attach a screenshot if
possible.

 
invalidservercertificate.PNG
64.4 KB View Download
Showing comments 135 - 234 of 234 Older

Comment 135 Deleted

Comment 136 by agl@chromium.org, Apr 9 2012

 Issue 122508  has been merged into this issue.

Comment 137 by Deleted ...@, Apr 9 2012

I didn't find a file named chrome_shutdown_ms.txt on my filesystem... but using "Clear Browsing Data..." (from beginning of time) seems to have resolved the issue. I've closed and opened Chrome several times over the last few hours, no repeat of the error yet. 

Comment 138 by Deleted ...@, Apr 9 2012

Still having issues here this morning.  Win7-64 Enterprise.  Cleared all browsing data, no luck. Reinstalled Chrome, no luck. Ctrl-W cleared it though, everything is fine now.

Google Chrome	18.0.1025.151 (Official Build 130497) m
OS	Windows
WebKit	535.19 (@113052)
JavaScript	V8 3.8.9.16
Flash	11,2,202,229
User Agent	Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1025.151 Safari/535.19

Comment 139 Deleted

Comment 140 by Deleted ...@, Apr 9 2012

Same issue as everyone else is reporting.

Found out I had a rootkit virus that was causing me the same grief - I ran almost everything against it, but it would not remove. I then ran combofix against it and now my https certificate issues are gone.

http://www.techspot.com/vb/topic178245.html

Labels: ReleaseBlock-Stable Mstone-18
One more follow-up question as we continue to investigate things:

Can a few people post the contents of chrome://gpu. Please save the file (the same way described in 3a of http://code.google.com/p/chromium/issues/detail?id=118706#c53 ) and attach it to this issue?

Thanks

Comment 143 Deleted

Comment 144 Deleted

Comment 145 by Deleted ...@, Apr 9 2012

chrome://gpu output attached... still having the issue 
chrome-gpu.txt
3.3 KB View Download
Attached is my Chrome GPU info.

Please, guys, don't post the whole info page as a message text here in thread. The best way is to save the page as html and attach as a file to your message. Please do help others who are reading this thread that way.

Cheers
chrome gpu.htm
76.6 KB View Download

Comment 147 by Deleted ...@, Apr 9 2012

gpu attached
chrome gpu.htm
125 KB View Download

Comment 148 by Deleted ...@, Apr 9 2012

chrome gpu.htm
72.8 KB View Download
Same here.
Deleting the "chrome_shutdown_ms.txt" file got me running for now.
See attached info, good luck and thanks in advance.
chrome_gpu.htm
125 KB View Download
system_info.png
204 KB View Download
chrome_version.htm
8.0 KB View Download

Comment 150 Deleted

They were captured after deletion, in a working state.
I'll try to break it and post back.

Ok, I have some fresh captures from both states.
Version (obviously?) stayed the same.
GPU has different info in the log between the two captures.
Conflicts shows a different number of modules loaded between the two captures.
chrome_conflicts_broken_state.htm
247 KB View Download
chrome_conflicts_working_state.htm
222 KB View Download
chrome_gpu_broken_state.htm
124 KB View Download
chrome_gpu_working_state.htm
125 KB View Download

Comment 153 by Deleted ...@, Apr 9 2012

Hello, have you noticed any CAPI2 Errors in Event Viewer of your PC? 

I had the same behaviour for https sites in chrome and got it fixed. (OS: Windows 7 x64bit).  

I am copy-pasting from my response on google groups:(https://groups.google.com/a/googleproductforums.com/forum/#!msg/chrome/1alZsHEeprc/jf6sC5bdHNMJ)

I don't know if this helps. I have two tcp dumps (with wireshark). 

- The one is with the problem that we are discussing with the invalid certificate. In this tcp dump i see that chrome is downloading "http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab" . So i downloaded it manualy and the results is in the images attached. 

- The second tcp dump was done after closing chrome with Ctrl+w, reopened it, visited gmail.com and everything worked as it was supposed to. In this tcpdump there was no visiting in the MS website (windowsupdate.com). 

I managed to fix it on my PC!!! :-)

Have you guys checked your Event Viewer under Administrative Tools? I realized that i had a lot of CAPI2 Errors with the message "Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: The specified procedure could not be found.
."

Actually, that one reminded me, that i had turned off Windows Updates. After enabling and did some updates, chrome started working again!!! (even if i close it from the X button and restart, all https sites are working)

So check your Event Viewer and do your updates. One good reason that i am thinking is that the local certificate of my PC were expired after a long period of no MS updates. I don't know why this happens to Chrome but i can think that chrome is using System Network Settings.

Waiting for your input as well. Right now i am doing a lot of updates, so I will come back in a while...

@ram...

I also have many CAPI2 errors in the event viewer.
My corporate security policy does not allow me to do updates.

I tried getting the authrootstl.cab file and installing it manually per MS' instructions, but that had no effect.
J.Cl... (and everyone who has commented so far): Was this record from chrome://gpu before or after you deleted the text file?

Sorry, it completely slipped my mind to indicate both states; a chrome://gpu log when the error happens (eg: chrome_shutdown_ms.txt is present) and a chrome://gpu log when the error is "fixed" (eg: chrome_shutdown_ms.txt isn't created / is manually deleted)

Comment 156 by Deleted ...@, Apr 9 2012

RSleevi - The chrome_shutdown_ms.txt file has never existed anywhere in my user profile directory, but the error still exists. 

Like J.Clay, I also have a large number of CAPI2 errors in the Event Log, but no pending Windows Updates (I just forced it to check, no updates available.) 
chrome gpu.htm
72.8 KB View Download
@shane...

Forgive me if this sounds patronizing.

Are you looking for it after launching chrome or while chrome is running?

If so, it disappears when you start chrome. I couldn't find it at first either.
Close chrome and refresh the appdata\local\google\chrome\user data directory. Delete chrome_shutdown_ms.txt before starting chrome.

Comment 158 by Deleted ...@, Apr 9 2012

RSleevi -

  No worries about patronizing. :) I was looking in the wrong place (and, oddly, windows search didn't find it either.) 

  I just tried deleting it prior to starting up - and was able to hit a few HTTPS addresses. However, once I shutdown the browser and restarted, the issue returns. I've attached the GPU output following the delete. 
chrome gpu_2.htm
72.8 KB View Download

Comment 159 by Deleted ...@, Apr 9 2012

@J.Cl... As i can see from your system info screenshot you dont have sp1 for win7 . Maybe you can get the offline installer of service pack1 for win7. Check http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=5842

I have also found an old thread here: http://code.google.com/p/chromium/issues/detail?id=5313

updating my system worked for me...

ram...:  Issue 5313  is unrelated.

However, thanks for confirming what I mentioned in http://code.google.com/p/chromium/issues/detail?id=118706#c79 . It appears that this only affects users who are not running Windows 7 SP1. While this is very useful information (as mentioned in comment #79), we'd still like to get to the root of this issue to understand what sort of adverse reaction is going on here.
@shane...

Yep, that's the same behavior I have. I just delete it before starting every time until this gets fixed.

@ram...

Thanks I wasn't aware there was one out yet. I'll give that a shot.
The standalone x64 SP1 didn't work... goin' for the full ISO!

Comment 162 Deleted

Comment 163 by Deleted ...@, Apr 9 2012

I downloaded sp1 for windows 7 and now it works for me . Thanks, I have been trying to figure our forever why my desktop worked fine but my laptop would not access the web pages.

Comment 164 by Deleted ...@, Apr 9 2012

Wait....are we saying that Google Chrome now requires SP1 on Win7 to function correctly with secure sites??

Comment 165 by Deleted ...@, Apr 9 2012

@rsleevi indeed 5313 is unrelated. 

If you need this, I've got two wireshark dumps - one session with the problem - and another without the https problem (closed tabs, restarted chrome and worked). Both are b4 updating to sp1 and the https site i was visiting is gmail.com.

Good luck with the root cause. Still very curious...

If it would help, I can abstain from installing SP1 for the moment to do some more prodding if needed.
J.Cl...: At the risk of punishing the helpful users, it would be rather helpful if you could abstain, just so we have a control.

I've spent quite a bit of time this past week/weekend/day trying to synthesize the failure, based on the information coming from chrome://conflicts and chrome://gpu, and have been unable to do so successfully so far. Having one or two controls will help us resolve this issue much quicker.

That said, once this issue is resolved, you definitely should consider upgrading to SP1. Lots of quality security fixes in there from Microsoft that you wouldn't want to be without =)

Comment 168 by Deleted ...@, Apr 9 2012

gpu not working.htm
124 KB View Download
gpu working.htm
124 KB View Download
My previous GPU info was for the case with deleted ms file and SSL sites loading fine.

Attached now is the one after I got the error. Comparing the two shows only two differences. Besides the date/time when the report was exported, the other one is 

Driver Information
Initialization time	174
in the no-problem case vs 176 in the case when there was the certificate error.

I am also one of those who can not update at the moment. But that's OK for now, it seems. 
GPU.7z
4.1 KB Download

Comment 170 by Deleted ...@, Apr 9 2012

Seems like a lot of people are working on this issue.

Is there any way the rest of us can be put on a "notification list" to find out when/how this issue is resolved?

Thanks!
-Jason
jason, if you star this bug, I will update it the minute we have a fix out the door.
@rsleevi

Sounds good, I'm fine just deleting the file to get it working for the moment.
Just let me know how I can help.
Hi jas...: Starring this bug is the best way to get continued updates as well as requests for further information.

One thing that would help is if you could save and attach copies of chrome://gpu and chrome://conflicts (as described in http://code.google.com/p/chromium/issues/detail?id=118706#c142 ), first without making any changes (eg: while it's broken), and then after deleting the file and relaunching chrome (eg: after it's fixed)

Thanks!

Comment 174 by kareng@google.com, Apr 10 2012

here you go: http://googlechromereleases.blogspot.com/2012/04/stable-channel-update.html

please let us know if you continue to see the issue once you upgrade to 18.0.1025.152

thank you so much for all the information and help!

Comment 175 by Deleted ...@, Apr 10 2012

Chrome auto-updated itself to the newest release and all seems well with the SSL issue; I can access most *.google.com sites now as well facebook.com among others.

Brilliant work, folks. It feels good to get back to using Chrome as my primary browser.

All - note Comment 174, which indicates 117371 may have regressed in this release. http://code.google.com/p/chromium/issues/detail?id=117371

Comment 176 by Deleted ...@, Apr 10 2012

This issue has hit me today. Never once had this problem.  I unistalled Chrome and reinstalled.  It worked for a few hours and now has happened again. 

What is causing this? 

Comment 177 by kareng@google.com, Apr 10 2012

bobduffy5 - which version of chrome are you using? we just pushed a fix and it's slowly making its way. 

Comment 178 by Deleted ...@, Apr 10 2012

I just received the auto update - everything seems to be working fine now. 

Great work, Google team! It's nice to have Chrome back...

Comment 179 by Deleted ...@, Apr 10 2012

Update has fixed my issue too - Win7 64bit, occurring on most but not all secure sites.
FYI. updating my status on 129

I've tried reinstalling Chrome, upgrading, the problem remains. 
And my PC at work are all installed Windows XP Professional SP3 so no Windows 7.
ele...: Given that the issue fixed by .152 should only have affected Windows 7 without any service packs, it's likely you're running into  Issue 120715  /  http://crbug.com/120715  or  Issue 117834  /  http://crbug.com/117834  . My instinct is that it is  Issue 117834 . To best determine this, please follow the steps from http://code.google.com/p/chromium/issues/detail?id=114709#c1 and report your results on  Issue 117834 . Thanks!

Comment 182 by Deleted ...@, Apr 10 2012

Thank you, update worked for me.

Comment 183 by Deleted ...@, Apr 10 2012

I'm good after update...thanks.
@rsleevi: will the update be pushed to the dev branch as well? I'm on 19.0 and having the same issue.
netman85am: We're currently looking at a different fix for the Dev branch, so I can't give a concrete ETA.

One thing that would be helpful would be trying the current Google Chrome Canary ( http://tools.google.com/dlpage/chromesxs ). This can run side-by-side with your existing (Stable/Beta/Dev) version, with a completely separate profile and settings. If you were to install the canary right now, you will likely find the issue exists there as well. However, as soon as the next canary is released (typically, nightly), you should hopefully find the issue resolved, without regressing  Issue 117371 .

If you (or anyone else currently running Dev) would give that a try, we'd love to hear your results and if you still continue to see the issue over the next day or two.
@rsleevi
Just installed canary 20.0.1096.1 and have no issues so far. Will keep you updated if it reappears in canary.
c186: Note, because Canary operates with a separate profile directory, you will need to exit and relaunch Chrome at least one (so that chrome_shutdown_ms.txt is created). Note that you will need to do the /opposite/ of the previous workaround, which is, make sure you close it via the red x in the top-right corner of the window, and NOT by pressing Control-W.

Certainly though, if you have any issues, please let us know.
Right. So far still happening, will let you know if next update fixes.

Comment 189 by Deleted ...@, Apr 10 2012

I'm working fine again after update to 152....thanks guys !

Comment 190 by Deleted ...@, Apr 10 2012

In continue to Comment #113: 

http://code.google.com/p/chromium/issues/detail?id=118706#c113

Upograde to V 18.0.1025.152 m did NOT help.
W7 SP1 64B

Comment 191 by Deleted ...@, Apr 10 2012

the .152 update seems to have fixed this for me as well.  Thanks for getting on top of this so quickly.  Great work!
18.0.1025.152 did NOT fix the issue.  Exact same SSL message still appear.  I'm on Windows XP.
Comment #190 (nam...) and Comment 192 (jca...)

Please see comment #181 ( http://code.google.com/p/chromium/issues/detail?id=118706#c181 ) and follow those steps. We'd love to be able to get you working as well. This applies to anyone else who is running Windows XP, as this issue only deals with Windows 7 64-bit.

Comment 194 by Deleted ...@, Apr 10 2012

In reply to #149 http://code.google.com/p/chromium/issues/detail?id=118706#c149

Unrelated to topic but your Windows product key is visible in that screenshot. Just thought I'll have you know...
OK, I submitted the information as you asked.  Interesting though that that bug was listed as being in Chrome 17, under which I saw no problem.
I just updated and the issue appears to be resolved for me as well.
Thank you for all your hard work Chrome Team!
@rsleevi, would you still like us to remain on the non-SP1 systems? I just got an offline installation of SP1 for Win7 64 but have no special preferences regarding updating the system just yet.

Just to report that 20.0.1096.1 dev-m, which just updated and relaunched the browser, still has the same issue. In case you were wondering. 
alen: If you can hold out a little bit longer, that'd be great.

My tentative fix just missed the cut-off window for the latest Dev. However, if you try the canary version (See comment #185), you shouldn't see the problem (after restarting Chrome appropriately to ensure chrome_shutdown_ms.txt is created)
Good. Testing with 20.0.1097.0 canary. The user profile created with chrome_shutdown_ms.txt file in it.
Getting Invalid Server Certificate on https://www.google.com
Testing with Facebook & Yahoo results in the same error message.

Were you referring to this version of Canary? 
Downloaded from http://tools.google.com/dlpage/chromesxs
Also to confirm that the trick with deleting the txt file works on the above version of Canary. Opening sites without problem in that case.
The .152 update seems to have solved the problem for me.Good work by the team.
Cc: rsleevi@chromium.org
 Issue 122930  has been merged into this issue.

Comment 203 by Deleted ...@, Apr 11 2012

Add me to the list of woe but I'm not on Windows, I'm on crunchbang linux. When I just now tried getting the .152 update with 'apt-get update', it does not seem to be available.  I currently have version 18.0.1025.151.
rid...: Then could you file a different issue? This issue only affects Windows 7 64-bit users who are not running SP1.

Including the information requested in http://code.google.com/p/chromium/issues/detail?id=118706#c181 in the new bug will be the best way to get you sorted.

Comment 205 by Deleted ...@, Apr 11 2012

Version 18.0.1025.152 seems to have fixed this problem for me. Thank you!
Cc: -rsleevi@chromium.org
alen.../c#200: Thanks for your continued patience and assistance while we investigate this.

I was hoping to do some further follow-up steps to work on resolving this bug completely. While we've already gone through some crazy steps, what I'm about to propose has a bit more technical complexity, and a lot more words, and unfortunately no pretty Microsoft documents to describe the process like there were in comment 16 / http://code.google.com/p/chromium/issues/detail?id=118706#c16




The steps I'm going to be following are taken largely from http://www.chromium.org/developers/testing/page-heap-for-chrome . However, because this page is targeted more towards Chromium developers, I'm going to reproduce the steps below with hopefully as much detail as needed to walk through the steps and fill in the gaps.

Before we begin, close all instances of "Chrome Canary" / Chrome SxS that you may have running.

1) First, we'll need to install the 32-bit Windows Debugging Tools.
  a) Visit http://msdn.microsoft.com/en-us/windows/hardware/gg463009
  b) Select "Install Debugging Tools for Windows as a Standalone Component", and follow the download directions
  c) As noted on the page from 1.a), during the installation wizard, you must select JUST "Debugging Tools", and should deselect everything else. There should only be five checkboxes, but only "Debugging Tools for Windows" needs to be checked.

2) At the end of the installation, you should have the Debugging Tools for Windows installed in a path such as "C:\Program Files (x86)\Debugging Tools for Windows (x86)". Please make sure such a path exists before continuing, and that within that folder there is a file called "gflags.exe"

3) You will need to add the Debugging Tools to your PATH. To do this, do the following steps:
  a) Click Start/Windows Icon, then Right-Click "Computer" and choose "Properties"
  b) From the left-hand side, click "Advanced System Settings". This requires administrative access.
  c) This will launch the "System Properties" dialog, with the "Advanced" tab selected. From this tab, click the "Environment Variables" button
  d) This will launch the "Environment Variables" dialog. Under the "User variables for <your username here>", there will likely be a variable called "PATH" already. Click "Edit". If there is not, click "New" instead. Note this is under "User Variables", not "System Variables"
  e) If there was one already (and you clicked "Edit"), at the beginning of "Variable Value" add the path from Step 2, followed by a semi-colon (eg: "C:\Program Files (x86)\Debugging Tools for Windows (x86);", without the quotes). If there wasn't one, for the variable name, enter "PATH" (without the quotes) and for the variable value enter the path from Step 2.
  f) Click OK to dismiss the "Edit/Add User Variable" dialog
  g) Click OK to dismiss the "Environment Variables" dialog
  h) click OK to dismiss the "System Properties" dialog.

4) Log out of your computer and log back in. This will make sure the settings take effect.

5) Similar to Comment #35 ( http://code.google.com/p/chromium/issues/detail?id=118706#c35 ), we're going to start a new "Command Prompt" by clicking Start/Windows Icon and searching for "Command Prompt". However, instead of left-clicking the icon in the start menu, Right Click, and choose "Run as Administrator"

6) In the new command prompt, type the following commands, without the "a)", "b)", etc. However, for commands in quotes, include the quotes. Do not close this window, we'll be coming back to it continuing through these steps.
  a) set CHROME_ALLOCATOR=winheap
  b) gflags /p /enable chrome.exe /full
  c) "%LocalAppData%\Google\Chrome SxS\Application\chrome.exe" --no-sandbox

7) Note that in 6c, we're launching Chrome Canary, not your normal chrome. This is because you indicated in comment #200 that Canary still demonstrates the problem. You should have a new Chrome Canary window open (although it may take some time, because of step 6b.

8) Hopefully, at this point, or close to it, Chrome will crash ;-) If it never loads, that may be OK too. Just wait a little.

9) If Chrome launches successfully, please save a copy of your chrome://version to attach or paste into this bug. Can you browse HTTPS sites ok?

10) Click the Red X to close the window, not the tab (so that Chrome creates the "chrome_shutdown_ms.txt file"). Then repeat step 6c), relaunching Chrome.

10) Does Chrome crash? If not, try navigating to an HTTPS site again. Can you browse OK?

11) Close Chrome again (it doesn't matter how)

12) In the Command Prompt, run the following command to reset Chrome to its default (and non-slow/non-crashy) behaviour. This is important, as forgetting to do this can make Chrome unbearably slow
  a) gflags /p /disable chrome.exe

13) You can now close the command prompt.

14) You can now undo the changes done in Step 3, by following the same steps, except deleting the variable (if added) or editing it to remove the changes (if edited)

15) Launch Chrome Canary one last time. Load chrome://crashes , and report back any crash IDs you have that have been within the past week.

Phew! That's it (hopefully!). Thanks very, very much if you're able to complete these steps, but I understand if they're a bit complex.

As I mentioned, we're pursuing a different solution for Canary and future versions of Chrome, one that we believe will be the best of both worlds, but in the mean time, we'd like to gather more data from users who encountered this, to see if there are new or interesting third-party modules that may be misbehaving or bugs in the OS to work around.

Thanks again for your continued patience and assistance.
Hi Ryan,

Attached is the log of the debugging session. I installed the Debugging Tools, set the path manually and ran Canary according to instructions. Attached is the About Version HTML file at this point.
No crashes. Can not open HTTPS sites. 

After closing the browser I confirmed that the ms file is in the profile directory (sxs, as opposed to the dev profile). Relaunching does not make a difference. At this point I assume that the first run was intended for a clean installation of Canary? Does that make any difference?
Just to confirm to myself, I deleted the ms file, ran Canary in the same manner and successfully opened https://www.google.com.
Closing Canary created the ms file again.

Disabled page heap. Now ran Canary by using the program shortcut pinned in the windows taskbar.
Saving chrome crashes. Please note that there aren't any in the previous week (?!). 

OK, that it is according to instructions. Please do let me know if we missed anything. Thanks for the very detailed instructions. However, I see no useful information in here. Everything seems to work as expected and there are no any errors in any of the logs.
I am attaching all the commands executed and their logs. This message is the chronological log of events with files being extracted at specified positions in the message.

Hope this is useful.
Cheers
log.7z
6.7 KB Download
Windows Application Event Log is full of errors:
"Failed extract of third-party root list from auto update cab at: <http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/authrootstl.cab> with error: -1073741702 (0xc000007a)."
These were mentioned before in this thread. 
Running .152 and issue is not fixed (Win7 wSP1)
doing comment #206 not possible on work-pc
comment #209: Please comment 193 for further steps -  http://code.google.com/p/chromium/issues/detail?id=118706#c193
alen: Thanks very much for doing this, and attaching the log of the commands.

From your invocation, it appears you used the 64-bit debugger toolkit ("C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x64"). That's likely why there weren't any crashes - as the 32-bit version of gflags needs to be used with Chrome (as it runs as a 32-bit exe).

Would it be possible to ask one more test run, this time indicating "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86" (if memory serves) as the path to the debugging tools?

Cheers
Hi, Ryan,

Not a problem. Here goes again. This time with 32-bit debugger.
Steps:
Prepare environment (same as before). Canary starts quickly again. No crashes. Invalid server certificate.

Closing the browser (x), relaunching. Invalid server certificate.

Closing the browser (x), deleting ms file, relaunching. Opening https://www.google.com works.
Closing the browser (x).

Stopping debugging options.

Launching via shortcut. Opening chrome://crashes. The results are the same as before - no recent crashes.

Attaching all log files. This time the debugger issued a message:
"Warning: pageheap.exe is running inside WOW64.
This scenario can be used to test x86 binaries (running inside WOW64)
but not native (IA64) binaries."

As you will see in the PATH, there is only path to x86 debugger listed. To confirm, here is the copy of running gflags, from Process Explorer - "C:\Program Files (x86)\Windows Kits\8.0\Debuggers\x86\gflags.exe". 
So, this time a correct debugger ran but the results are the same. Canary has not crashed once. Everything seemed pretty much the usual. I have not tried any extras apart from opening www.google.com via HTTPS.

Do let me know if there is anything else I can do to help. 
Cheers
log2.7z
6.1 KB Download
Cc: eroman@chromium.org
Knowing the internals of the browser code, do you think any of this could be caused by security software like Avira Antivirus or Comodo Firewall with Defense?
I have not seen any warnings in their logs, though. There are only two notification flags "Access Memory" for Canary for the time I was running it.
[as in http://help.comodo.com/topic-72-1-284-2975-View-Defense+-Events.html]
I can't see them in the more detailed view. 
Anyway, nothing seems to have been blocked as far as I can tell.

Comment 215 by Deleted ...@, Apr 13 2012

Open "chrome://conflicts" and check for conflict with "rlvknlg.exe" - an Adware/Spyware named "RelevantKnowledge". Uninstall and reboot:)
Comment #215: As demonstrated by the number of users who included their chrome://conflicts, that isn't this issue. However, that is at least partially suspect for  Issue 117834 , so I'm glad you were able to resolve your issue.

Comment 217 by Deleted ...@, Apr 14 2012

Just got back from a week away to see that I've still got this issue, even after a upgrade. Is there anything you'd like me to do before going to sp1 - Win7 64bit?
chrome://conflicts: Modules (98) - No conflicts detected

Google Chrome	19.0.1084.24 (Official Build 131971) beta-m
OS	Windows
WebKit	536.5 (@113812)
JavaScript	V8 3.9.24.12
Flash	11,2,202,229
User Agent	Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.24 Safari/536.5
Command Line	"C:\Users\A&E\AppData\Local\Google\Chrome\Application\chrome.exe" --flag-switches-begin --flag-switches-end
Executable Path	C:\Users\A&E\AppData\Local\Google\Chrome\Application\chrome.exe
Profile Path	C:\Users\A&E\AppData\Local\Google\Chrome\User Data\Default

Comment 218 by Deleted ...@, Apr 15 2012

I realize this thread relates to Windows 7 users.  Where can I find a thread addressing this issue (https: invalid certificates) for Windows XP users? The ones I've found related to Facebook and Twitter but they're not a problem for me.  Lots of https sites work but it seems that banking and government sites in particular have invalid certificates according to Chrome (but not according to Firefox or Internet Explorer).
I have this problem with Chrome 18.01025.162 on Mac OS X 10.6.8. Only when going to Penfed.org. Works fine using Safari. It started 10 days ago or so. 
comment #217: This is not yet fixed in 19/20, as we're investigatinge a different fix. Going to SP1 is a reasonable fix as well.

comment #218: Follow the steps in http://code.google.com/p/chromium/issues/detail?id=114709#c1 and attach to  Issue 117834 . That will help determine what your issue is, but it's not this issue.

Comment #219: Please see  Issue 122500  / http://code.google.com/p/chromium/issues/detail?id=122500 

Comment 221 by Deleted ...@, Apr 15 2012

RE: #220 (comment #218)  Thanks for the reply.  Will do, but I don't understand attaching it to  issue 117834  since my problem seems to me to be in no way to be related to  issue 117834 .  That issue relates to Facebook logon and "weak signature algorithm" error messages. I have no problem logging on to Facebook, and get NO error message(s) when I do. 

Mine problem relates to invalid site certificates (and failure to successfully logon to https sites.)

Comment 222 by Deleted ...@, Apr 17 2012

Re #217 & #220, SP1 installed (after an evening backup) - everything fine now with v19.0.1084.24
comment #210: files are attached :)
Windows7 wSP1 running .162
google_Certificate.p7b
2.2 KB Download
CertificationPath.png
26.3 KB View Download
error.jpg
117 KB View Download
Labels: GoogleFeedback
The below data is provided based on user reports in 'GoogleFeedback'.
Chrome Versions		: 18.0.1025.162 

300+ users have reported this issue in GoogleFeedback since 4/12

What steps will reproduce the problem?
1. Try browsing web pages in Chrome browser

What is the expected result?
Web pages should render the sites normally

What happens instead?
Page displays "Invalid Server Certificate" for some websites. 

Most of the users have reported this issue while login to facebook.com

For more details, refer the report URLs below:
http://goto.google.com/220307679
http://goto.google.com/220184459
http://goto.google.com/156333571

For more user reports, refer the Cluster URL below:
http://goto.google.com/1012637

NOTE: We are unable to reproduce this issue across different versions of Chrome 

300+ users have reported this issue in GoogleFeedback since 4/12

Comment 225 by sleevi@google.com, Apr 18 2012

ranavdk: We should probably track those in a new bug. .162 should not be affected by this issue (laforge reverted on M18, this should be resolved, was left open for M19). Sounds like there's some sort of new regression?
@Sleevi - Created new bug - http://goto.google.com/124111.

250 reports for v18.0.1025.162 

Comment 227 by Deleted ...@, Apr 19 2012

It's been happening to me for 4 weeks now.
@comment 226: I cannot even open your link :-)
Can you post the full one?
error2.jpg
106 KB View Download

Comment 229 by Deleted ...@, Apr 20 2012

Same error for me with the lastest version. I cannot even log into Google Mail - I have to use FireFox instead (I am behind a proxy).


Security Error - Google Chrome_2012-04-20_09-07-00.png
94.6 KB View Download

Comment 230 by fja...@gmail.com, Apr 20 2012

Encountered this today when accessing http://www.intax.in.gov/
(which SOMETIMES says Invalid Server Certificate when it redirects to the https:// version of the site)

This is Chrome 19 beta on OS X Lion.

It also happens on Chrome 18 stable on my mom's iMac (running OS X Lion). She called me this morning asking me about the error. She had to use Safari to work around the problem.

Apparently Mac Chrome doesn't have chrome://conflicts/ because it says invalid URL when I go there.

Google Chrome	19.0.1084.24 (Official Build 131971) beta
OS	Mac OS X
WebKit	536.5 (@113812)
JavaScript	V8 3.9.24.12
Flash	11.2.202.229
User Agent	Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.24 Safari/536.5
Command Line	 /Applications/Google Chrome.app/Contents/MacOS/Google Chrome --flag-switches-begin --flag-switches-end
Executable Path	/Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Profile Path	/Users/mday/Library/Application Support/Google/Chrome/Default


invalidserver.png
155 KB View Download
Labels: Restrict-AddIssueComment-Commit
Status: Fixed
Marking this particular issue fixed, as the common root issue has been resolved on M18 and M19.

For any new users encountering this, please submit new bugs using the New Issue template - http://code.google.com/p/chromium/issues/entry - being careful to fill out all requested/available details. I'll be watching and duplicating common roots, but given that different users experience this for different reasons, I want to be sure that every bug is being kept separate and not lost in the noise.

Comment #228 - #230: Thanks for reporting this. To make sure your issues are not lost, I'd ask if you can file a new issue with the information requested on the new issue template.

Thanks!
Project Member

Comment 232 by bugdroid1@chromium.org, Mar 10 2013

Labels: -Area-Internals -Internals-Network-SSL -Feature-Security -Mstone-18 Cr-Security M-18 Cr-Internals Cr-Internals-Network-SSL
Project Member

Comment 233 by bugdroid1@chromium.org, Mar 13 2013

Labels: -Restrict-AddIssueComment-Commit Restrict-AddIssueComment-EditIssue
Labels: hasTestcase
Showing comments 135 - 234 of 234 Older

Sign in to add a comment