New issue
Advanced search Search tips

Issue 851891 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 9
Cc:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

Few tabs seems to be crashed when machine is left idle for ~40 minutes

Project Member Reported by pnangunoori@chromium.org, Jun 12 2018

Issue description

Chrome Version: #69.0.3455.0
OS: Windows 10 

What steps will reproduce the problem?
(1) Launched Chrome with the flag #network-service enabled
(2) Open few tabs and work for 3-4 hours.
(3) Let the machine be idle for ~40 minutes.
(4) Launch Chrome after ~40 minutes.

What is the expected result?
User should be able to use Chrome normally.

What happens instead?
Few tabs in the Chrome seems to be crashed. 
Crash ID Generated - 1bc2f81a591ee4ca

Note: 
1. Assuming this could be because of the flag #network-service enabled
2. Will update with the further observations if the issue is observed once again.
3. Also, observed that all the gmail accounts got logged out.

Stack Trace:
Thread 5 (id: 0x4478) CRASHED [EXCEPTION_ACCESS_VIOLATION_READ @ 0x00000004 ] MAGIC SIGNATURE THREAD
Stack Quality100%Show frame trust levels
0x00007ffd07f58873	(chrome_child.dll -net_adapters.cc:43 )	network::NetToMojoPendingBuffer::Complete(unsigned int)
0x00007ffd08d02e0f	(chrome_child.dll -url_loader.cc:878 )	network::URLLoader::CompletePendingWrite()
0x00007ffd08d02d94	(chrome_child.dll -url_loader.cc:740 )	network::URLLoader::DidRead(int,bool)
0x00007ffd067a4a94	(chrome_child.dll -task_annotator.cc:101 )	base::debug::TaskAnnotator::RunTask(char const *,base::PendingTask *)
0x00007ffd067a33ab	(chrome_child.dll -message_loop.cc:319 )	base::MessageLoop::RunTask(base::PendingTask *)
0x00007ffd0679b067	(chrome_child.dll -message_loop.cc:373 )	base::MessageLoop::DoWork()
0x00007ffd0679d7e9	(chrome_child.dll -message_pump_win.cc:478 )	base::MessagePumpForIO::DoRunLoop()
0x00007ffd0679d677	(chrome_child.dll -message_pump_win.cc:56 )	base::MessagePumpWin::Run(base::MessagePump::Delegate *)
0x00007ffd0679abc0	(chrome_child.dll -run_loop.cc:102 )	base::RunLoop::Run()
0x00007ffd0679a9cf	(chrome_child.dll -thread.cc:337 )	base::Thread::ThreadMain()
0x00007ffd07e3c803	(chrome_child.dll -platform_thread_win.cc:91 )	base::`anonymous namespace'::ThreadFunc
0x00007ffd51572783	(KERNEL32.DLL + 0x00012783 )	BaseThreadInitThunk
0x00007ffd53fe0d50	(ntdll.dll + 0x00070d50 )	RtlUserThreadStart
 
Labels: Inhouse-HYD-Reported
Just to update other additional observation - 

In the same time frame, there was another machine where we didn't see any tab crashes. Hence, attaching the variations of Good & Bad machines and GPU of bad machine.

Thanks!
BadWin10-GPU.txt
17.0 KB View Download
BadBuildVariations.html
6.6 KB View Download
GoodBuildVariations.html
6.6 KB View Download

Comment 3 by dxie@google.com, Jun 19 2018

Status: Available (was: Untriaged)
Cc: dxie@chromium.org
Status: WontFix (was: Available)
Unable to reproduce the issue after multiple attempts to reproduce, left machine with 15 tabs over the weekend as well as couple of hours haven't observed any crashes. 

Marking the bug as wontfix for now.

Sign in to add a comment