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

Issue 708495 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Jul 26
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Browser crash is observed after clicking on 'honey' extension from wrench menu.

Reported by vku...@etouch.net, Apr 5 2017

Issue description

Chrome Version: 58.0.3029.54 (Official Build) 04f6db09151b28679cc587f355235df935d8bcda-refs/branch-heads/3029@{#586}(64 Bit).
OS: Mac 10.11.6

What steps will reproduce the problem?
(1)Launch chrome and install any 5 extensions from https://chrome.google.com/webstore/category/extensions
(2)Resize browser from R.H.S and install "honey" extension.
(3)Right click on extension >hide in chrome menu,click on extension twice from wrench and right click > keep in toolbar (repeat 2-3 time),observe.

Actual: Browser crash is observed after clicking on 'honey' extension from wrench menu.
Crash ID fd5acbe1-a7d7-481b-b069-fada9aadfadf (Server ID: bf2181c210000000)
Crash ID 12323c96-7aa2-48c8-a6a2-436872f8bdac (Server ID: d558c7c210000000)

Expected: Browser should not crash after clicking on 'honey' extension from wrench menu.

This is a Mac 10.11.6 specific regression issue broken in 'M57' and below is the manual regression range
Good Build: 57.0.2986.0  
Bad Build:  57.0.2987.0

Note: Issue not seen on Win & Linux OS 


 
Actual_Extensions.mov
4.8 MB Download
Cc: rbasuvula@chromium.org
Labels: hasbisect-per-revision
Owner: liaoyuke@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build:57.0.2986.0 (Revision:444600).
Bad build:57.0.2987.0 (Revision:444943).

You are probably looking for a change made after 444900 (known good), but no later than 444901 (first known bad).

CHANGE-LOG URL:
---------------
https://chromium.googlesource.com/chromium/src/+log/a2fd53c7b0a8b9f0c657e94257059879c8fe7a27..0b662a9cf9d75b3223e9fad83228e8f6d515cfe4

From the CL above, assigning the issue to the concern owner

@liaoyuke: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Review-Url: https://codereview.chromium.org/2640783005
Note : Mac specific issue and Able to reproduce in latest Canary #59.0.3063.0.

Stack Trace:
------------
Thread 0 CRASHED [EXC_BAD_INSTRUCTION / EXC_I386_INVOP @ 0x00007fff9486be6a ] MAGIC SIGNATURE THREAD
Stack Quality81%Show frame trust levels
0x00007fff9486be6a	(AppKit + 0x003d0e6a )	-[NSApplication _crashOnException:]
0x00007fff9486bdc3	(AppKit + 0x003d0dc3 )	-[NSApplication reportException:]
0x00007fff84f3286a	(CoreFoundation + 0x0017c86a )	__handleUncaughtException
0x00007fff8614c487	(libobjc.A.dylib + 0x00016487 )	_objc_terminate()
0x00007fff8e3e800d	(libc++abi.dylib + 0x0002400d )	std::__terminate(void (*)())
0x00007fff8e3e7c8e	(libc++abi.dylib + 0x00023c8e )	__cxa_rethrow
0x00007fff86148c22	(libobjc.A.dylib + 0x00012c22 )	objc_exception_rethrow
0x00007fff84e3ef6a	(CoreFoundation + 0x00088f6a )	CFRunLoopRunSpecific
0x00007fff8a523934	(HIToolbox + 0x00030934 )	RunCurrentEventLoopInMode
0x00007fff8a52376e	(HIToolbox + 0x0003076e )	ReceiveNextEventCommon
0x00007fff8a5235ae	(HIToolbox + 0x000305ae )	_BlockUntilNextEventMatchingListInModeWithFilter
0x00007fff944e3df5	(AppKit + 0x00048df5 )	_DPSNextEvent
0x00007fff944e3225	(AppKit + 0x00048225 )	-[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:]
0x000000010c936a9f	(Google Chrome Framework -chrome_browser_application_mac.mm:187 )	__71-[BrowserCrApplication nextEventMatchingMask:untilDate:inMode:dequeue:]_block_invoke
0x000000010cd807a9	(Google Chrome Framework + 0x019b07a9 )	base::mac::CallWithEHFrame(void () block_pointer)
0x000000010c9369d8	(Google Chrome Framework -chrome_browser_application_mac.mm:186 )	-[BrowserCrApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
0x00007fff944d7d7f	(AppKit + 0x0003cd7f )	-[NSApplication run]
0x000000010cd9037d	(Google Chrome Framework -message_pump_mac.mm:637 )	base::MessagePumpNSApplication::DoRun(base::MessagePump::Delegate*)
0x000000010cd8f9fb	(Google Chrome Framework -message_pump_mac.mm:210 )	base::MessagePumpCFRunLoopBase::Run(base::MessagePump::Delegate*)
0x000000010cdae562	(Google Chrome Framework -run_loop.cc:37 )	base::RunLoop::Run()
0x000000010c93c4d8	(Google Chrome Framework -chrome_browser_main.cc:1990 )	ChromeBrowserMainParts::MainMessageLoopRun(int*)
0x000000010c10e8f3	(Google Chrome Framework -browser_main_loop.cc:1176 )	content::BrowserMainLoop::RunMainMessageLoopParts()
0x000000010c1115b1	(Google Chrome Framework -browser_main_runner.cc:141 )	content::BrowserMainRunnerImpl::Run()
0x000000010c10a46b	(Google Chrome Framework -browser_main.cc:46 )	content::BrowserMain(content::MainFunctionParams const&)
0x000000010c8f3d5f	(Google Chrome Framework -content_main_runner.cc:793 )	content::ContentMainRunnerImpl::Run()
0x000000010c8f3025	(Google Chrome Framework -content_main.cc:20 )	content::ContentMain(content::ContentMainParams const&)
0x000000010b3d3b7a	(Google Chrome Framework -chrome_main.cc:112 )	ChromeMain
0x000000010b16bd99	(Google Chrome -chrome_exe_main_mac.c:85 )	main
0x00007fff8a4ee5ac	(libdyld.dylib + 0x000035ac )	start
Cc: pbomm...@chromium.org gov...@chromium.org
CC'ing @goving and @pbommana, request to please check if this could be any Stable blocker for MAC OS (Only)on M57.

Thanks.!
Cc: rsesek@chromium.org
I am not sure what additional steps lead to the crash but so far I wasn't able to reproduce the crash on 3 different machines.

cc'ing 	rsesek@ based on similar crash which was fixed( issue#637270 ) in past, This is top#3 Browser crash on latest Chrome stable i.e., 57.0.2987.133. Please find details from here : https://goto.google.com/fejzc

Note : The stack quality is just 49% and look more of Apple related bug,Please correct me if I a wrong.
Owner: rbasuvula@chromium.org
@rbasuvula, my change is test only on iOS, shouldn't have caused the problem, so I'm re-assigning this back to you.
Cc: abdulsyed@chromium.org ligim...@chromium.org
Labels: M-58
Checked with rsesek@, this is not an M57 stable blocker. 
Project Member

Comment 6 by sheriffbot@chromium.org, Apr 5 2017

Labels: FoundIn-M-58 Fracas
Users experienced this crash on the following builds:

Mac Beta 58.0.3029.41 -  0.28 CPM, 17 reports, 15 clients (signature -[NSApplication _crashOnException:])

If this update was incorrect, please add "Fracas-Wrong" label to prevent future updates.

- Go/Fracas
Labels: -Fracas Fracas-Wrong
Labels: -M-57 -M-58 -hasbisect-per-revision -FoundIn-M-58 M-60
Owner: vku...@etouch.net
This crash started in M53 and is spiking in stable channels. Historical data below.

57.0.2987.133	12.15%	9715	
56.0.2924.87	39.52%	31602	
55.0.2883.95	30.22%	24167	
54.0.2840.98	3.15%	2519	
53.0.2785.143	0.39%	315

vkupte@etouch.net are you still able to reproduce in latest chrome versions? If yes, please it try a bisect again.

We will target this for M60.
Issue 716289 has been merged into this issue.
Project Member

Comment 10 by PranavkRobot, Jul 16

Labels: crash-BugNoRepro
Crash analysis has not encountered any reports for this bug for the past 90 days. We have added the label 'crash-BugNoRepro'

Crash analysis will be automatically closing the bug in 10 days. If you do not want Crash analysis to automatically close the bug, please remove the label 'crash-BugNoRepro'. If you have any feedback on this feature, please contact pranavk@
Project Member

Comment 11 by PranavkRobot, Jul 26

Labels: crash-BugNoRepro-Closed
Status: WontFix (was: Assigned)
Crash analysis has not encountered any reports for this bug for the past 90 days. Hence as per the comment 10 days ago, we are closing the bug and setting the status to WontFix. If you have any feedback on this feature, please contact pranavk@

Sign in to add a comment