New issue
Advanced search Search tips

Issue 820569 link

Starred by 5 users

Issue metadata

Status: Duplicate
Merged: issue 816628
Owner: ----
Closed: Mar 2018
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Chrome 66.0.3359.22 opens immediately crashes closed multiple machines rollback to 66.0.3355.4 fixes issue

Reported by collin.c...@blueprairie.com, Mar 9 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3355.4 Safari/537.36

Steps to reproduce the problem:
1. Upgrade working 66.0.3355.4 to 66.0.3359.22
2. Restart/start Chrome (even with --no-experiments and --disable-extensions --disable-plugins)
3. Chrome flashes open then closes and can see crash reporter process running report
4. Note this is on almost a dozen Win7x64 all coming from 66.0.3355.4 and NONE can start once upgraded to 66.0.3359.22.  NOT a profile issue since 100% of them then open again successfully without any issues upon rolling back manually to saved 66.0.3355.4.

What is the expected behavior?
Normal upgrade experience

What went wrong?
EVERYTHING - Browser no longer opens at all.

Crashed report ID: No had to roll back just to open chrome but have debug log and have full crash logs

How much crashed? Whole browser

Is it a problem with a plugin? N/A 

Did this work before? Yes 

Chrome version: 66.0.3359.22  Channel: dev
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

Yes - on multiple machines all logged this in their local debug logs upon self-update to 66.0.3359.22 indicating errors:

[0311/180225.290:ERROR:exception_snapshot_win.cc(87)] thread ID 3148 not found in process
[0311/180225.291:WARNING:crash_report_exception_handler.cc(60)] ProcessSnapshotWin::Initialize failed
[0312/093332.698:ERROR:exception_snapshot_win.cc(87)] thread ID 7476 not found in process
[0312/093332.699:WARNING:crash_report_exception_handler.cc(60)] ProcessSnapshotWin::Initialize failed
[0312/132518.772:ERROR:exception_handler_server.cc(524)] ConnectNamedPipe: The pipe is being closed. (0xE8)
[0312/162927.372:ERROR:exception_handler_server.cc(524)] ConnectNamedPipe: The pipe is being closed. (0xE8)
[0312/163109.778:ERROR:exception_handler_server.cc(524)] ConnectNamedPipe: The pipe is being closed. (0xE8)
[0312/163128.681:ERROR:exception_handler_server.cc(524)] ConnectNamedPipe: The pipe is being closed. (0xE8)
[0312/182850.314:ERROR:exception_handler_server.cc(524)] ConnectNamedPipe: The pipe is being closed. (0xE8)
[0313/070226.465:ERROR:exception_handler_server.cc(524)] ConnectNamedPipe: The pipe is being closed. (0xE8)
[0313/220531.459:ERROR:exception_handler_server.cc(524)] ConnectNamedPipe: The pipe is being closed. (0xE8)
[0315/021103.799:ERROR:exception_handler_server.cc(524)] ConnectNamedPipe: The pipe is being closed. (0xE8)
[0316/195814.983:ERROR:exception_handler_server.cc(524)] ConnectNamedPipe: The pipe is being closed. (0xE8)
[0316/222452.042:ERROR:exception_handler_server.cc(524)] ConnectNamedPipe: The pipe is being closed. (0xE8)
[0317/010901.323:ERROR:exception_handler_server.cc(524)] ConnectNamedPipe: The pipe is being closed. (0xE8)
[0321/111204.551:ERROR:process_info.cc(343)] VirtualQueryEx: Access is denied. (0x5)
[0321/111204.553:ERROR:process_info.cc(564)] ReadMemoryInfo failed
[0321/111204.553:ERROR:process_reader_win.cc(233)] ReadMemory at 0x7feced029a0 of 12 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[0321/111204.553:WARNING:process_snapshot_win.cc(68)] ReadMemory ExceptionInformation failed
[0321/111204.553:WARNING:crash_report_exception_handler.cc(60)] ProcessSnapshotWin::Initialize failed
[0321/111204.553:ERROR:scoped_process_suspend.cc(38)] NtResumeProcess: An attempt was made to access an exiting process.  (0xc000010a)
[0328/145150.281:ERROR:exception_snapshot_win.cc(87)] thread ID 8812 not found in process
[0328/145150.282:WARNING:crash_report_exception_handler.cc(60)] ProcessSnapshotWin::Initialize failed
[0428/082634.204:ERROR:prune_crash_reports.cc(58)] Database Pruning: Failed to remove report 29e7881d-1908-4733-9e56-c57c3870628b
[0428/082634.206:ERROR:prune_crash_reports.cc(58)] Database Pruning: Failed to remove report 8555e69d-f5a3-44ab-bf7d-ce99762576f4
[0428/082634.207:ERROR:prune_crash_reports.cc(58)] Database Pruning: Failed to remove report 5509cdd6-f881-4ca0-a166-0ed8870c6dfa
[0604/063826.507:ERROR:process_reader_win.cc(242)] ReadMemory at 0x3f7fff80 of 512 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[0604/063826.508:ERROR:crash_report_exception_handler.cc(116)] WriteEverything failed
[0615/002351.841:ERROR:registration_protocol_win.cc(56)] CreateFile: The system cannot find the file specified. (0x2)
[0814/155546.918:ERROR:process_info.cc(380)] UncheckedAllocate
[0814/155546.968:ERROR:process_info.cc(380)] UncheckedAllocate
[0309/131307.933:ERROR:process_reader_win.cc(242)] ReadMemory at 0x12ffff93 of 512 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[0309/131307.933:ERROR:crash_report_exception_handler.cc(116)] WriteEverything failed
[0309/131423.950:ERROR:process_reader_win.cc(242)] ReadMemory at 0x17ffff98 of 512 bytes failed: Only part of a ReadProcessMemory or WriteProcessMemory request was completed. (0x12B)
[0309/131423.951:ERROR:crash_report_exception_handler.cc(116)] WriteEverything failed

But again - simply renaming the application folder to application.old and restoring 66.0.3355.4's application folder in-place results in Chrome's immediate opening.
 

Comment 1 by huan...@gmail.com, Mar 9 2018

I have encountered the same problem w/ Windows 10.0.16299.248 x64.

Comment 2 by mba...@gmail.com, Mar 9 2018

Same problem here, W7 (SP1) HP 64bit.

Versione 66.0.3359.22 (Build ufficiale) dev (a 64 bit)

But, after I removed the Chrome/Application/debug.log file, magically it seems to work again. No need to revert to previous version.

Hope this help.

Comment 3 by huan...@gmail.com, Mar 9 2018

Not sure what happened. But I did not see debug.log file in Chrome/Application/ folder.
Negative @mba.......removing the debug.log file has absolutely no effect on any of the many machines I've tested it on.  As of now, rolling back and then having to block auto-updates (a pain) is the only workaround.

This is horrible and I really hope gets assigned a high priority considering this is flat out a bad build in the channel to the DEV community that kills the entire browser and creates quite the headache.

Comment 5 by woxxom@gmail.com, Mar 10 2018

Duplicate of  issue 818176  fixed in 67.0.3360.0.
Not sure what the plans are regarding v66, see  https://crbug.com/816628#c20 

Comment 6 by jer...@gmail.com, Mar 10 2018

Same issue for me in dev channel on windows 10.
Same issue, Dev build (66.0.3359.22) crashes upon loading but Canary (67.0.3360.0) works.

Comment 8 by cnardi@chromium.org, Mar 10 2018

Mergedinto: 816628
Status: Duplicate (was: Unconfirmed)
Looks like a fix was just merged; duping this bug to  bug 816628  as it seems progress is tracked there.
Thanks for the quick action and update!

Sign in to add a comment