New issue
Advanced search Search tips

Issue 632619 link

Starred by 3 users
Status: Duplicate
Owner:
sebmarchand@chromium.org
Closed: Aug 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

EMET crashes Chrome

Reported by kyvenr...@gmail.com, Jul 29 2016 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.34 Safari/537.36

Steps to reproduce the problem:
1. Install EMET 5.5
2. Enable EAF+ protection on chrome.exe
3. Open Chrome

What is the expected behavior?
Chrome opens without crashing.

What went wrong?
Since Chrome Beta updated to 53 EMET has been crashing all tabs and plugins upon opening. It gives the error "EMET detected EAF+ (Guard Page) mitigation and will close the application." 

Disabling EAF+ on chrome.exe allows Chrome to open normally.

Crashed report ID: 6f767c98-22fe-44f2-9b7d-48eeb031700e (Server ID: 4d8ed8be00000000)

How much crashed? Whole browser

Is it a problem with a plugin? No 

Did this work before? Yes Chrome 52 and earlier

Chrome version: 53.0.2785.34  Channel: beta
OS Version: 10.0
Flash Version:

Comment 1 by durga.behera@chromium.org, Aug 2 2016

Components: Platform>NaCl
Labels: TE-NeedsfurtherTriage
Thanks for the report,added respective dev team to take a look into this to further update on it.

Stack Trace:
==============
Thread 0 CRASHED [EXCEPTION_STACK_BUFFER_OVERRUN @ 0x0000017ba394c360 ] MAGIC SIGNATURE THREAD
0x0000017ba394c360		
0x00007ffdf3cc7614	(chrome_child.dll -nacl_dep_qualify.c:25 )	NaClAttemptToExecuteDataAtAddr
0x00007ffdf3cab823	(chrome_child.dll -sel_qualify.c:26 )	NaClRunSelQualificationTests
0x00007ffdf3ca95bd	(chrome_child.dll -sel_main_chrome.c:225 )	LoadApp
0x00007ffdf3ca66e5	(chrome_child.dll -nacl_listener.cc:433 )	NaClListener::OnStart(nacl::NaClStartParams const &)
0x00007ffdf3ca4e48	(chrome_child.dll -ipc_message_templates.h:121 )	IPC::MessageT<NaClProcessMsg_Start_Meta,std::tuple<nacl::NaClStartParams>,void>::Dispatch<NaClListener,NaClListener,void,void ( NaClListener::*)(nacl::NaClStartParams const &)>(IPC::Message const *,NaClListener *,NaClListener *,void *,void ( NaClListener::*)(nacl::NaClStartParams const &))
0x00007ffdf3ca5c4b	(chrome_child.dll -nacl_listener.cc:244 )	NaClListener::OnMessageReceived(IPC::Message const &)
0x00007ffdf23608f7	(chrome_child.dll -ipc_channel_proxy.cc:284 )	IPC::ChannelProxy::Context::OnDispatchMessage(IPC::Message const &)
0x00007ffdf237db7c	(chrome_child.dll -task_annotator.cc:51 )	base::debug::TaskAnnotator::RunTask(char const *,base::PendingTask const &)
0x00007ffdf237cf5d	(chrome_child.dll -message_loop.cc:493 )	base::MessageLoop::RunTask(base::PendingTask const &)
0x00007ffdf237d300	(chrome_child.dll -message_loop.cc:624 )	base::MessageLoop::DoWork()
0x00007ffdf237c54e	(chrome_child.dll -message_pump_win.cc:727 )	base::MessagePumpForIO::DoRunLoop()
0x00007ffdf27beba6	(chrome_child.dll -message_pump_win.cc:140 )	base::MessagePumpWin::Run(base::MessagePump::Delegate *)
0x00007ffdf27bfa71	(chrome_child.dll -message_loop.cc:457 )	base::MessageLoop::RunHandler()
0x00007ffdf27bfa00	(chrome_child.dll -run_loop.cc:35 )	base::RunLoop::Run()
0x00007ffdf3ca586b	(chrome_child.dll -nacl_listener.cc:236 )	NaClListener::Listen()
0x00007ffdf3ca4a69	(chrome_child.dll -nacl_main.cc:54 )	NaClMain(content::MainFunctionParams const &)
0x00007ffdf2f030e4	(chrome_child.dll -chrome_main_delegate.cc:920 )	ChromeMainDelegate::RunProcess(std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &,content::MainFunctionParams const &)
0x00007ffdf2f030b9	(chrome_child.dll -content_main_runner.cc:431 )	content::RunNamedProcessTypeMain(std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &,content::MainFunctionParams const &,content::ContentMainDelegate *)
0x00007ffdf245e5c5	(chrome_child.dll -content_main_runner.cc:785 )	content::ContentMainRunnerImpl::Run()
0x00007ffdf245e4f4	(chrome_child.dll -content_main.cc:20 )	content::ContentMain(content::ContentMainParams const &)
0x00007ffdf283b97c	(chrome_child.dll -chrome_main.cc:84 )	ChromeMain
0x00007ff606668b3e	(chrome.exe -main_dll_loader_win.cc:185 )	MainDllLoader::Launch(HINSTANCE__ *)
0x00007ff606662b5b	(chrome.exe -chrome_exe_main_win.cc:262 )	wWinMain
0x00007ff6066f5b55	(chrome.exe -exe_common.inl:255 )	__scrt_common_main_seh
0x00007ffe26758101	(KERNEL32.DLL + 0x00018101 )	BaseThreadInitThunk
0x00007ffe26efc5b3	(ntdll.dll + 0x0005c5b3 )	RtlUserThreadStart

Comment 2 by sebmarchand@chromium.org, Aug 2 2016

Mergedinto: 586515
Owner: sebmarchand@chromium.org
Status: Duplicate (was: Unconfirmed)
I'm looking at this. Thanks for the repro steps.

Comment 3 by sebmarchand@chromium.org, Aug 2 2016 

Please note that there's some known compatibility issues between EMET and Chrome and so we recommend to not use it on Chrome: https://www.chromium.org/Home/chromium-security/chromium-and-emet

Comment 4 by sebmarchand@chromium.org, Aug 4 2016

Labels: -TE-NeedsfurtherTriage
►

Sign in to add a comment