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

Issue 661737 link

Starred by 3 users
Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
dtapu...@chromium.org
█ durga.behera@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

After using Flash application and going idle, the Aw Snap unresponsive alert pops up.

Reported by ero...@gmail.com, Nov 2 2016 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36

Steps to reproduce the problem:
It is not consistent to reproduce. The error happens when both using the application and when on other windows and idle.

The same operations have worked before the Chrome and Flash player updates.

What is the expected behavior?

What went wrong?
When idle or working in the app, the Aw Snap dialog appears. Clicking "Wait" gives access to the page again and to use the app, but after 2-3 more minutes, it gives the Aw Snap page again.

Crashed report ID: e65a5f78-e685-4658-8680-f19a26988a94

How much crashed? Just one plugin

Is it a problem with a plugin? Yes Flash

Did this work before? Yes Pre-54.0.2840.71

Chrome version: 54.0.2840.87  Channel: stable
OS Version: 7, 8, 10
Flash Version: Shockwave Flash 23.0.0.205

This is affecting multiple users of the app. If more information is needed, I would be glad to provide what I can.

Here are other crash report IDs in case they help. These are from several different computers.

Crash ID d31d84a4-812b-4f9f-8276-2606a6359e90 (Server ID: a623908700000000)

Crash ID fd4237fc-f0f4-47eb-9ac4-4039850c013d (Server ID: 472814eb00000000)

Crash ID 06645533-6ff2-4741-a27b-38bdce06d0d7 (Server ID: 9ceba60700000000)

Crash ID 525df291-6d4d-494b-9582-0dc9e16d19cc (Server ID: 3e43808b00000000)

Crash ID 538d2eba-77c1-4b7c-ba6a-51db420b92b6

Crash ID 97f36313-2c69-416c-8fce-2736d5cd628d

Crash ID bc23acfa-32a5-414b-bf57-4091648ead7c

Crash ID 634570cd-3b5d-4a41-840b-c5701ba92a58

Comment 1 by durga.behera@chromium.org, Nov 3 2016

Cc: dtapu...@chromium.org
Labels: M-54 Needs-Feedback
All the crash report Ids have same Stack trace and similar to Issue 615090, and currently being worked on.
Anyhow could you please help with the consistent repro steps(urlss,credentials if can be shared) to triage further.
dtapuska@ : cced you based on the updates on the similar work done on Issue 615090.

Stack trace:
==============================================
xThread 0 MAGIC SIGNATURE THREAD
Stack QualityUnknownShow frame trust levels
0x00007ffc40684ed4	(ntdll.dll + 0x000a4ed4 )	NtWaitForSingleObject
0x00007ffc3cc275fe	(KERNELBASE.dll + 0x000175fe )	WaitForSingleObjectEx
0x00007ffc08316621	(chrome_child.dll -waitable_event_win.cc:65 )	base::WaitableEvent::TimedWait(base::TimeDelta const &)
0x00007ffc08316f1c	(chrome_child.dll -message_pump_default.cc:71 )	base::MessagePumpDefault::Run(base::MessagePump::Delegate *)
0x00007ffc085bd56d	(chrome_child.dll -message_loop.cc:457 )	base::MessageLoop::RunHandler()
0x00007ffc085bd4fc	(chrome_child.dll -run_loop.cc:35 )	base::RunLoop::Run()
0x00007ffc0877be34	(chrome_child.dll -message_loop.cc:295 )	base::MessageLoop::Run()
0x00007ffc0877c042	(chrome_child.dll -renderer_main.cc:197 )	content::RendererMain(content::MainFunctionParams const &)
0x00007ffc0877b037	(chrome_child.dll -content_main_runner.cc:418 )	content::RunNamedProcessTypeMain(std::basic_string<char,std::char_traits<char>,std::allocator<char> > const &,content::MainFunctionParams const &,content::ContentMainDelegate *)
0x00007ffc0868809d	(chrome_child.dll -content_main_runner.cc:785 )	content::ContentMainRunnerImpl::Run()
0x00007ffc08687fcc	(chrome_child.dll -content_main.cc:20 )	content::ContentMain(content::ContentMainParams const &)
0x00007ffc088e5a0c	(chrome_child.dll -chrome_main.cc:84 )	ChromeMain
0x00007ff6d1178b3e	(chrome.exe -main_dll_loader_win.cc:185 )	MainDllLoader::Launch(HINSTANCE__ *)
0x00007ff6d1172b5b	(chrome.exe -chrome_exe_main_win.cc:262 )	wWinMain
0x00007ff6d1205b0d	(chrome.exe -exe_common.inl:255 )	__scrt_common_main_seh
0x00007ffc3def8363	(KERNEL32.DLL + 0x00008363 )	BaseThreadInitThunk
0x00007ffc40645e90	(ntdll.dll + 0x00065e90 )	RtlUserThreadStart

Thread 14 CRASHED [0x0517a7ed / 0x00000000 @ 0x00007ff6d11babcb ]
Stack QualityUnknownShow frame trust levels
0x00007ff6d11babcb	(chrome.exe -crashpad_win.cc:144 )	DumpProcessWithoutCrash
0x00007ff6d11babfd	(chrome.exe -crashpad_win.cc:159 )	crash_reporter::internal::`anonymous namespace'::DumpProcessWithoutCrashThread
0x00007ffc3def8363	(KERNEL32.DLL + 0x00008363 )	BaseThreadInitThunk
0x00007ffc40645e90	(ntdll.dll + 0x00065e90 )	RtlUserThreadStart

Comment 2 by ero...@gmail.com, Nov 4 2016 

I appears I don't have permissions to view issue 615090. Can you grant me permissions so I can review it?

Comment 3 by dtapu...@chromium.org, Nov 4 2016 

issue 615090 contains some internal URIs and doesn't in fact contain any more additional relevant information than in Comment #1 here.

If you can come up with a reproduction step or some type of test credentials we can try with the flash application (seems to be revolutionehr) that would be helpful.

Comment 4 by ero...@gmail.com, Nov 4 2016 

Thanks. I'm working on getting a set of credentials for this and will post them here as soon as I can.
Project Member

Comment 5 by sheriffbot@chromium.org, Nov 12 2016

Labels: -Needs-Feedback Needs-Review
Owner: durga.behera@chromium.org
Thank you for providing more feedback. Adding requester "durga.behera@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

Comment 6 by pucchakayala@chromium.org, Nov 14 2016

Labels: -Needs-Review Needs-Feedback
Marking with "Needs-Feedback" as we are still waiting on the feedback from the reporter as per # 3 & #4

Comment 7 by ajha@chromium.org, Jan 30 2017

Cc: durga.behera@chromium.org
Owner: ----
Gentle ping to get an update on this issue or please confirm if the issue is still seen on the latest stable version(56.0.2924.76) or not?

Comment 8 by dtapu...@chromium.org, Oct 10 2017

Status: WontFix (was: Unconfirmed)
Closing due to lack of feedback requested but not provided. If the issue still happens please open a new issue with the details requested.
►

Sign in to add a comment