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

Issue 762151 link

Starred by 2 users

Issue metadata

Status: Duplicate
Owner: ----
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome crashes when redocking (Win 10)

Reported by arimende...@gmail.com, Sep 5 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36

Steps to reproduce the problem:
1. Have Chrome open when computer is not docked
2. Dock computer (possibly lose internet connection briefly while re-docking)
3. Chrome crashes and requires full computer reboot

What is the expected behavior?
Chrome does not crash

What went wrong?
Chrome is unresponsive.  If I force close Chrome, then I cannot reopen Chrome until  I reboot my computer.

Crashed report ID: 2a56b345-3c04-4b8c-81df-8791ffbd9973

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? N/A 

Chrome version: 58.0.3029.81  Channel: n/a
OS Version: 10.0
Flash Version:
 
Cc: rbasuvula@chromium.org
Components: UI>Browser
Labels: Needs-Milestone Needs-Feedback
Thanks for filing the issue! Could you please provide the server id of the crash from chrome://crashes and if possible,Please create new profile without extensions and apps.Re-check once in latest chrome builds(stable/canary)and let us know the observations which would help us to triage the issue further.

Thanks in Advance.
Server id: 64adbe8c10c08b31
Project Member

Comment 3 by sheriffbot@chromium.org, Sep 6 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "rbasuvula@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
This issue is fixed, please update to latest chrome version.
Cc: ranjitkan@chromium.org
Labels: Needs-Feedback
arimendelson1: Request you to please provide an update as per above comment.

Thanks.!
This did happen again today in 61.0.3163.79.

Crash id: b7b236586aa90028
Project Member

Comment 7 by sheriffbot@chromium.org, Oct 19 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "ranjitkan@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 8 by ajha@chromium.org, Nov 1 2017

Labels: Needs-Feedback
The attached crash id in C#6: b7b236586aa90028 is from chrome version: 58.0.3029.81.

arimendelson1@: Could you please recheck on the latest stable(62.0.3202.75) and attach any crash id from there, if this is still an issue.


I may have pasted the wrong crash id.  I think I recreated this in 61.0.3163.79, can you check these crash ids?  I believe these were the same issue but I am not positive.


9ec24c8d5106dc0a
7f16c02703974508

Project Member

Comment 10 by sheriffbot@chromium.org, Nov 1 2017

Cc: ajha@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "ajha@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Mergedinto: 615090
Status: Duplicate (was: Unconfirmed)
The stack trace of crash id: 9ec24c8d5106dc0a is as follows:
Thread 0 (id: 11236) MAGIC SIGNATURE THREAD
Stack Quality100%Show frame trust levels
0x77d0e59c	(ntdll.dll + 0x0006e59c )	NtWaitForSingleObject
0x74faaf28	(KERNELBASE.dll + 0x000caf28 )	WaitForSingleObjectEx
0x74faae81	(KERNELBASE.dll + 0x000cae81 )	WaitForSingleObject
0x0fb55509	(chrome_child.dll -waitable_event_win.cc:80 )	base::`anonymous namespace'::WaitUntil
0x0fb54e08	(chrome_child.dll -waitable_event_win.cc:127 )	base::WaitableEvent::TimedWaitUntil(base::TimeTicks const &)
0x0fb54838	(chrome_child.dll -message_pump_default.cc:59 )	base::MessagePumpDefault::Run(base::MessagePump::Delegate *)
0x0fd2b528	(chrome_child.dll -message_loop.cc:369 )	base::MessageLoop::Run()
0x0fd2b4df	(chrome_child.dll -run_loop.cc:111 )	base::RunLoop::Run()
0x0fe72e6d	(chrome_child.dll -renderer_main.cc:219 )	content::RendererMain(content::MainFunctionParams const &)
0x0fd0e656	(chrome_child.dll -content_main_runner.cc:407 )	content::RunNamedProcessTypeMain(std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &,content::MainFunctionParams const &,content::ContentMainDelegate *)
0x0fd0e503	(chrome_child.dll -content_main_runner.cc:686 )	content::ContentMainRunnerImpl::Run()
0x0fdcd2f8	(chrome_child.dll -main.cc:469 )	service_manager::Main(service_manager::MainParams const &)
0x0fdcd10f	(chrome_child.dll -content_main.cc:19 )	content::ContentMain(content::ContentMainParams const &)
0x0fdcd0a9	(chrome_child.dll -chrome_main.cc:139 )	ChromeMain
0x009d59fe	(chrome.exe -main_dll_loader_win.cc:199 )	MainDllLoader::Launch(HINSTANCE__ *,base::TimeTicks)
0x009d21de	(chrome.exe -chrome_exe_main_win.cc:266 )	wWinMain
0x00a60a97	(chrome.exe -exe_common.inl:253 )	__scrt_common_main_seh
0x754262c3	(KERNEL32.DLL + 0x000162c3 )	BaseThreadInitThunk
0x77d00f78	(ntdll.dll + 0x00060f78 )	__RtlUserThreadStart
0x77d00f43	(ntdll.dll + 0x00060f43 )	_RtlUserThreadStart

As per above stack trace it looks similar to issue id: 615090. Hence, merging into issue id: 615090.

Thanks...!!
Here's one more crash... this may help confirm what you are seeing:

49d18590a32a6445 

Sign in to add a comment