Can you please give the exact URL's for that websites that are crashing

https://wizzair.com/#/
https://www.easyjet.com/us/

Still happens with Version 67.0.3372.1 (Official Build) canary (64-bit)

Here's a dump file from Windows

Deleted: chrome.exe.15564.dmp 3.1 MB

chrome.exe.15564.dmp 3.1 MB Download

The dump file indicates PlatformSensorReaderWin (Ambient Light Sensor API) i.e. "Blink>Sensor" component.

https://www.kayak.com/ also crashes on Version 67.0.3373.0 (Official Build) canary (64-bit)

I cannot reproduce on the Reported version, can you please disable extensions and try on a new chrome profile?

I tried that, but the result is the same - crash.
Maybe that's because of the recent Windows update to Version 1709 OS Build 16299.309?

BTW, what I'm getting is:
Google Chrome has stopped working
A problem caused the program to stop working correctly.
Windows will close the program and notify you if a solution is available.

Tested in chrome # 67.0.3372.0 and Canary #67.0.3374.0 on win 10.0 and not able to reproduce the issue.Please find the screen shots for your reference.

@qwer1304: Could you please let me know if i have missed anything and if possible,Please create new profile without extensions and apps.Re-check once in latest builds and let us know the observations of the issue which would help us to triage the issue further.

Thanks in Advance.

Deleted: 822629.PNG 2.9 MB

	822629.PNG 2.9 MB View Download

I tried that, including a completely new install of Chrome 67.0.3372.0 w/o any extensions and a new profile and it still happens.
I also tried this on another computer and it did NOT happen.
My conclusion that it's specific to THIS computer.
The difference is that THIS computer has Wind 10 Version 1709 OS Build 16299.309 and the other one has Win 10 16299.248.
The former JUST came out, so maybe it's the one that triggers this behavior.

So, please retest this with Win 10 Version 1709 OS Build 16299.309.

Also, I can provide the full dump, but let me know where to upload it to since it's bigger than 10MB.

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

Tested the issue using #67.0.3375.0 on Win 10 (1607, 14393.2068) and could not reproduce the issue by navigating to above mentioned URL's.

@Reporter: Could you please upgrade Chrome to latest version #67.0.3375.0 and check if you still face the issue? If so attach a Crash I'd from chrome://crashes.

Thanks!!

Tested on Chrome Version 67.0.3375.0 (Official Build) canary (64-bit) on Version 1709 OS Build 16299.309 and the problem PERSISTS.

There's no crash file (Chrome is closed by Windows).

I can provide Windows mini-dump and/or full dump.

This seems to be related to SPECIFIC LATEST Windows version 1709 OS Build 16299.309. Please test on THAT version.

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

I managed to connect to these sites in Safe Boot With Networking mode. So it seems that the problem is in Win 10 version or its interaction with Chrome.

Unable to reproduce the issue on Windows 10 with chrome canary #67.0.3377.0 for the provided urls in comment #2, able to navigate to the sites as  expected and didn't observe any crash.

Since TE doesn't able to reproduce this issue, adding TE-NeedsTriageHelp label for further triage.

Please note that you MUST try this on Windows Version 1709 OS Build 16299.309!!!!

Do NOT try this on EARLIER versions, it does NOT repeat!

You MUST USE Windows Version 1709 OS Build 16299.309!!!!

I ran Chrome with --enable-logging --v=1 flags and am attaching the log file that was collected before it crashed.
This is for Chrome Version 67.0.3378.0 (Official Build) canary (64-bit)

Deleted: chrome_debug.log 1.6 MB

chrome_debug.log 1.6 MB View Download

Installed CHROMIUM and the crash did NOT occur.
Did a completely FRESH install of Chrome Canary after deleting the previous install including the user directory and the crash DID occur.

And now it works!
Absolutely no idea what has changed

Today I installed update March 22, 2018—KB4089848 (OS Build 16299.334) and crashes are BACK!

Here's dump info from Chrome Version 67.0.3381.0 (Official Build) canary (64-bit) on www.wizzair.com
Looks like heap corruption.
Maybe SyzyAsan version would help to locate the error.


Microsoft (R) Windows Debugger Version 10.0.16299.91 X86
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\david\AppData\Local\CrashDumps\chrome.exe.18604.dmp]
User Mini Dump File: Only registers, stack and portions of memory are available


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\code\symbols*http://msdl.microsoft.com/download/symbols
Deferred                                       SRV*c:\code\symbols*https://chromium-browser-symsrv.commondatastorage.googleapis.com
Symbol search path is: SRV*c:\code\symbols*http://msdl.microsoft.com/download/symbols;SRV*c:\code\symbols*https://chromium-browser-symsrv.commondatastorage.googleapis.com
Executable search path is: 
Windows 10 Version 16299 MP (4 procs) Free x64
Product: WinNt, suite: SingleUserTS Personal
16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Debug session time: Tue Mar 27 10:40:36.000 2018 (UTC + 3:00)
System Uptime: not available
Process Uptime: 0 days 0:00:21.000
................................................................
................................................................
.
Loading unloaded module list
....
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(48ac.558): Unknown exception - code c0000374 (first/second chance not available)
ntdll!NtWaitForMultipleObjects+0x14:
00007ff9`eebb0e14 c3              ret
0:046> .symfix; .reload
................................................................
................................................................
.
Loading unloaded module list
....
0:046> !analyze -v
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for chrome.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for chrome.exe - 
*** ERROR: Module load completed but symbols could not be loaded for mbae64.dll
GetUrlPageData2 (WinHttp) failed: 12002.

DUMP_CLASS: 2

DUMP_QUALIFIER: 400

CONTEXT:  (.ecxr)
rax=0000000000000000 rbx=00000000c0000374 rcx=0000000000000003
rdx=00007ff9eeb2cd29 rsi=0000000000000001 rdi=00007ff9eec6c6e0
rip=00007ff9eec0879b rsp=000000fae73fee70 rbp=000002906b089e90
 r8=0000000000000000  r9=0000000000000000 r10=0000000000000000
r11=0000000100000000 r12=000002906fe65c70 r13=0000000000000000
r14=0000000000000000 r15=00007ff9b3e0bf58
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202
ntdll!RtlReportCriticalFailure+0x97:
00007ff9`eec0879b eb00            jmp     ntdll!RtlReportCriticalFailure+0x99 (00007ff9`eec0879d)
Resetting default scope

FAULTING_IP: 
ntdll!RtlReportCriticalFailure+97
00007ff9`eec0879b eb00            jmp     ntdll!RtlReportCriticalFailure+0x99 (00007ff9`eec0879d)

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ff9eec0879b (ntdll!RtlReportCriticalFailure+0x0000000000000097)
   ExceptionCode: c0000374
  ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 00007ff9eec6c6e0

PROCESS_NAME:  chrome.exe

ERROR_CODE: (NTSTATUS) 0xc0000374 - A heap has been corrupted.

EXCEPTION_CODE: (NTSTATUS) 0xc0000374 - A heap has been corrupted.

EXCEPTION_CODE_STR:  c0000374

EXCEPTION_PARAMETER1:  00007ff9eec6c6e0

WATSON_BKT_PROCSTAMP:  5ab9d9ba

WATSON_BKT_PROCVER:  67.0.3381.0

PROCESS_VER_PRODUCT:  Google Chrome

WATSON_BKT_MODULE:  ntdll.dll

WATSON_BKT_MODSTAMP:  e508fc03

WATSON_BKT_MODOFFSET:  f879b

WATSON_BKT_MODVER:  10.0.16299.334

MODULE_VER_PRODUCT:  Microsoft® Windows® Operating System

BUILD_VERSION_STRING:  10.0.16299.64 (WinBuild.160101.0800)

MODLIST_WITH_TSCHKSUM_HASH:  1bb64aa87fa21deaeefb7ce2c2ffc81fc6cbf12b

MODLIST_SHA1_HASH:  9b75d4a258c332a70b40bb33521f3fbd7faae11f

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

DUMP_FLAGS:  94

DUMP_TYPE:  1

ANALYSIS_SESSION_HOST:  DAVID-HP

ANALYSIS_SESSION_TIME:  03-27-2018 10:45:59.0064

ANALYSIS_VERSION: 10.0.16299.91 x86fre

THREAD_ATTRIBUTES: 
ADDITIONAL_DEBUG_TEXT:  Followup set based on attribute [Heap_Error_Type] from Frame:[0] on thread:[PSEUDO_THREAD] ; Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

LAST_CONTROL_TRANSFER:  from 00007ff9eec0fcda to 00007ff9eec0879b

FAULTING_THREAD:  ffffffff

THREAD_SHA1_HASH_MOD_FUNC:  6bf660ace0bbcfa1d956a3a3e951870e4e85dc2c

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  0f341b12fc67d336a618b5899b750e25953d6f4e

OS_LOCALE:  ENG

PROBLEM_CLASSES: 

    ID:     [0n249]
    Type:   [ACTIONABLE]
    Class:  Addendum
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Add
    Data:   Add
            String: [BlockNotBusy]
    PID:    [0x48ac]
    TID:    [0x558]
    Frame:  [2] : ntdll!RtlpLogHeapFailure

    ID:     [0n250]
    Type:   [HEAP_CORRUPTION]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x558]
    Frame:  [0] : ntdll!RtlReportCriticalFailure

    ID:     [0n248]
    Type:   [DOUBLE_FREE]
    Class:  Addendum
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [0x48ac]
    TID:    [0x558]
    Frame:  [2] : ntdll!RtlpLogHeapFailure

BUGCHECK_STR:  HEAP_CORRUPTION_ACTIONABLE_BlockNotBusy_DOUBLE_FREE

DEFAULT_BUCKET_ID:  HEAP_CORRUPTION_ACTIONABLE_BlockNotBusy_DOUBLE_FREE

PRIMARY_PROBLEM_CLASS:  HEAP_CORRUPTION

STACK_TEXT:  
00007ff9`eec6c748 00007ff9`eebc419a ntdll!RtlFreeHeap+0x8da6a
00007ff9`eec6c750 00007ff9`bb86d6a1 AcLayers!NS_FaultTolerantHeap::APIHook_RtlFreeHeap+0x9581
00007ff9`eec6c758 00007ff9`eaf1cb1b ucrtbase!_free_base+0x1b
00007ff9`eec6c760 00007ff9`eaf1c98a ucrtbase!__crt_state_management::wrapped_invoke<void +0x2a
00007ff9`eec6c768 00007ff9`e6741486 SensorsApi!CSensorV2::`vector deleting destructor'+0x26
00007ff9`eec6c770 00007ff9`e672baeb SensorsApi!Microsoft::WRL::Details::RuntimeClassImpl<Microsoft::WRL::RuntimeClassFlags<2>,1,0,0,ISensor,ISensorPower,Microsoft::WRL::FtmBase>::Release+0x2b
00007ff9`eec6c778 00007ff9`b3e0b0d1 chrome!GetHandleVerifier+0xdef011
00007ff9`eec6c780 00007ff9`b3e0bed3 chrome!GetHandleVerifier+0xdefe13
00007ff9`eec6c788 00007ff9`b30360ff chrome!GetHandleVerifier+0x1a03f
00007ff9`eec6c790 00007ff9`b3035bfc chrome!GetHandleVerifier+0x19b3c
00007ff9`eec6c798 00007ff9`b3035658 chrome!GetHandleVerifier+0x19598
00007ff9`eec6c7a0 00007ff9`b3035499 chrome!GetHandleVerifier+0x193d9
00007ff9`eec6c7a8 00007ff9`b3034c15 chrome!GetHandleVerifier+0x18b55
00007ff9`eec6c7b0 00007ff9`b30336fa chrome!GetHandleVerifier+0x1763a
00007ff9`eec6c7b8 00007ff9`b40d6714 chrome!RelaunchChromeBrowserWithNewCommandLineIfNeeded+0x5f5f5
00007ff9`eec6c7c0 00007ff9`ee541fe4 kernel32!BaseThreadInitThunk+0x14
00007ff9`eec6c7c8 00007ff9`eeb7f061 ntdll!RtlUserThreadStart+0x21


THREAD_SHA1_HASH_MOD:  db3950846e556f0f9344ac2fb31b697154ad7f27

FOLLOWUP_IP: 
ucrtbase!_free_base+1b
00007ff9`eaf1cb1b 85c0            test    eax,eax

FAULT_INSTR_CODE:  840fc085

SYMBOL_STACK_INDEX:  2

SYMBOL_NAME:  ucrtbase!_free_base+1b

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ucrtbase

IMAGE_NAME:  ucrtbase.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  !heap ; ** Pseudo Context ** HeapPseudo ** Value: c438390 ** ; kb

BUCKET_ID:  HEAP_CORRUPTION_ACTIONABLE_BlockNotBusy_DOUBLE_FREE_ucrtbase!_free_base+1b

FAILURE_EXCEPTION_CODE:  c0000374

FAILURE_IMAGE_NAME:  ucrtbase.dll

BUCKET_ID_IMAGE_STR:  ucrtbase.dll

FAILURE_MODULE_NAME:  ucrtbase

BUCKET_ID_MODULE_STR:  ucrtbase

FAILURE_FUNCTION_NAME:  _free_base

BUCKET_ID_FUNCTION_STR:  _free_base

BUCKET_ID_OFFSET:  1b

BUCKET_ID_MODTIMEDATESTAMP:  0

BUCKET_ID_MODCHECKSUM:  f65c3

BUCKET_ID_MODVER_STR:  10.0.16299.248

BUCKET_ID_PREFIX_STR:  HEAP_CORRUPTION_ACTIONABLE_BlockNotBusy_DOUBLE_FREE_

FAILURE_PROBLEM_CLASS:  HEAP_CORRUPTION

FAILURE_SYMBOL_NAME:  ucrtbase.dll!_free_base

FAILURE_BUCKET_ID:  HEAP_CORRUPTION_ACTIONABLE_BlockNotBusy_DOUBLE_FREE_c0000374_ucrtbase.dll!_free_base

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/chrome.exe/67.0.3381.0/5ab9d9ba/ntdll.dll/10.0.16299.334/e508fc03/c0000374/000f879b.htm?Retriage=1

TARGET_TIME:  2018-03-27T07:40:36.000Z

OSBUILD:  16299

OSSERVICEPACK:  15

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  768

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt SingleUserTS Personal

USER_LCID:  0

OSBUILD_TIMESTAMP:  1976-06-22 09:45:20

BUILDDATESTAMP_STR:  160101.0800

BUILDLAB_STR:  WinBuild

BUILDOSVER_STR:  10.0.16299.64

ANALYSIS_SESSION_ELAPSED_TIME:  22636

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:heap_corruption_actionable_blocknotbusy_double_free_c0000374_ucrtbase.dll!_free_base

FAILURE_ID_HASH:  {7ded92b2-7b16-55fa-4d99-56f02892348d}

Followup:     MachineOwner
---------

Attached is windbg console output from Chrome Version 67.0.3384.0 (Official Build) canary (64-bit).
The sequence of steps:
1.Launch windbg
2.Open chrome exe file
3.Hit F5 once
-> chrome opens with single tab
4.Enter wizzair.com in address bar and hit Enter

Deleted: wizzair_log.TXT 12.3 KB

wizzair_log.TXT 12.3 KB View Download

AcLayers!NS_FaultTolerantHeap::APIHook_RtlFreeHeap implies that Chrome is running under the Fault Tolerant heap, which it shouldn't be, as that could well mask the true source of the crash; https://blogs.msdn.microsoft.com/oldnewthing/20120125-00/?p=8463

If this involves an HP Spectre or Lenovo Yoga, see  issue 806977  which is causing similar hard crashes with no crash report for certain commerce sites.

That problem has been traced to the Windows 1803 monthly updates & bad USB3 drivers, which may be cured by other events - but only effects chrome.

There has been significant tracing progress on  bug 806977 , which now needs attention.. Thanks

This is indeed HP Spectre x360.
Problems started BEFORE 1803 update.
Funny enough, they had suddenly gone away BEFORE 1803 update too.
After 1803 they did NOT reappear and updating BIOS to F50 (from F46) did NOT break the system.

gwer@ #28 - The first 2 irregularities (pre 1803, gone away) cited are consistent with the reports at 
https://productforums.google.com/forum/#!topic/chrome/Y61R9SAEPBc

Before 1803, i.e. 1709, Windows updates would sometimes fix the problem, or they would otherwise be healed spontaneously.  I'd have to look back to see if a Chrome update ever fixed the problem.

Re: After 1803 they did NOT reappear 

Since the 1803 public release May 2018, each Windows cumulative update seems to break the commerce sites.  The June 17134.112 update broke at least one user (F50 I believe)

Re: and updating BIOS to F50 (from F46) did NOT break the system.

There are no reports of a BIOS update breaking chrome, an update was however sometimes a fix.

There are not enough reports to assert consistent breakage with the Win updates, even at the individual PC level.  Stability and breakage seem spotty.

If broken, the USB3 eXtensible host controller uninstall-recovery does seem to fix the problem.. until possibly the next windows update.

If you could tag in on the forum thread
  https://productforums.google.com/forum/#!topic/chrome/Y61R9SAEPBc
with your hardware and bios specs and the USB3 eXtensible and root hub version and dates, I would appreciate it.

gwer@ - Thanks for the driver notes in the forum thread.

Given the number of Spectre 360s and the low incidence of reports, I suspect there are other local factors that impact windows update installing old USB drivers occasionally.  Your spectre remained stable after the 17134.112 update, others broke again.

Your USB drivers look current and have been updated with 1803.  The eXtensible host controller with the initial 1803 install and root hub with the 17134.112 update (from early June).  They have been updated since your pre 1803 spontaneous cure.

per #23 Mar 25, the 1709 16299.334 update broke Chrome again.  You mention it's been good since before 1803 and after.  Do you know when it started working after Mar 25?

I see by your date format usage, that you are not in the US.  I don't know how regional support factors in, hopefully not.

Since disabling JS avoids the crash (but makes the site useless), it's clear it's Blink related.  Since the crashes involve old (2016?), pre 1803 USB drivers, I'm not sure Blink is at fault, although this could be considered a form of faile backward compatibility.

If you can fill in the pre 1803 when cured timeline and let me know if the July Windows update is OK, I'd appreciate it.

larrylac@: Not sure when the problem cured itself.
The language is English (US), but I changed to date format to European
I'll update how it goes after July update

Same issue on my Spectre x360 visiting fidelity.com
I can provide dump files and logs if needed.

This is a duplicate of  issue 806977  opened 29Jan18.

There are almost daily reports of this commerce site crash in the Forum:
See https://productforums.google.com/forum/#!topic/chrome/Y61R9SAEPBc
or  https://productforums.google.com/forum/#!topic/chrome/iNPoJAQ2ORU
There are many other threads, I've tried to redirect them to the first one.

There is another (#5) Blink>Sensor error from GDB
NativeSensorCollectionNotifThread:Sensor is being stopped before thread started polling - here
https://productforums.google.com/d/msg/chrome/zbjlfo8HJPI/UkCjF9vDBwAJ

The problem is re-triggered (for some) after each Windows monthly cumulative update.  

The workaround to uninstall the USB3 Extensible HC and scan for changes which re-installs the same 17134.1 driver works for ~90% of users, may be less often for Yoga.

There are developers who see this at their sites (Lance Giles) who have volunteered access if needed.

Any help would be appreciated.

Boyd (Lenovo Yoga) reports 7/18 here that even when refreshing the USB3 HC driver does not fix the problem, uninstalling and blocking the refresh does.
https://productforums.google.com/d/msg/chrome/i88slCB85wU/naDZC4R-AQAJ

This seems to confirm it is not a side-effect of refresh that fixes the problem, but the actual USB use, probably in JavaScript cookie access.

As the OP qwer1 is now posting to  issue 806977 , I will be posting mostly there too.

After the update and with HP Spectre X360 13 F51 firmware update problem reoccured.
Disabled HID Sensor Collection V2 and problems is GONE!
Then did Hardware Scan Changes => nothing happened.
Re-enabled HID Sensor Collection V2 => problem STILL GONE!

I'm looking into this issue (which appears to be a duplicate of 789344) and also going to try to pull in crash reporter folks who can look into why none of these crashes seem to generate crash reports.