Repeated GPU crash while using lucidchart and Google Spreadsheets |
|||
Issue descriptionChrome Version : 63.0.3239.132 OS Version: OS X 10.13.3 What steps will reproduce the problem? 1. Visit go/lucidchart to get an account. 2. Open a graph and play with it. 3. In a new window, open a Google Spreadsheet with a graph of 60 rows, 8 data columns as stacked lines. 4. Use the web UI of the two apps for several minutes, may take 30 minutes to reproduce. What is the expected result? Works. What happens instead of that? Get a "WebGL process crashed" yellow infobar from time to time. Crash ID: go/crash?stbtiq=ee49b88d50f20c93 Please provide any additional information below. Attach a screenshot if possible. - MBP 2012-era, nvidia GT 650M - 3 external monitors connected. UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
,
Feb 8 2018
I have a Lucidchart account now though not yet edit access. Could you please share with me a graph that's affected?
,
Feb 9 2018
Shared the sheet.
,
Feb 12 2018
,
Feb 13 2018
M-A: please also provide the link of the needed Google Sheet. Kai, James: could one of you volunteer to triage this bug once we have all the needed pieces? We could try to turn off virtualized GL contexts at the compositor level to see if that works around the problem, mainly to understand why the crash is happening. Here is the stack trace from the above crash report: Thread 0 (id: 5678) CRASHED [0x00000000 / 0x00000000 @ 0x00007fff6c153e3e ] MAGIC SIGNATURE THREAD Stack Quality66%Show frame trust levels 0x00007fff6c153e3e (libsystem_kernel.dylib + 0x0001be3e ) __pthread_kill 0x00007fff6c0b0311 (libsystem_c.dylib + 0x0005d311 ) abort 0x00007fff5cf4815c (libGPUSupportMercury.dylib + 0x0000215c ) gpusGenerateCrashLog 0x00007fff3eef457e (GeForceGLDriver + 0x0031957e ) 0x00007fff5cf49541 (libGPUSupportMercury.dylib + 0x00003541 ) gpusSubmitDataBuffers 0x00007fff3eeefa3d (GeForceGLDriver + 0x00314a3d ) 0x00007fff3eeef728 (GeForceGLDriver + 0x00314728 ) 0x0000000108871703 (Google Chrome Framework -gl_context_cgl.cc:252 ) gl::GLContextCGL::MakeCurrent(gl::GLSurface*) 0x0000000108862e02 (Google Chrome Framework -gl_context.cc:321 ) gl::GLContext::MakeVirtuallyCurrent(gl::GLContext*, gl::GLSurface*) 0x00000001089a7dca (Google Chrome Framework -gles2_cmd_decoder.cc:4386 ) gpu::gles2::GLES2DecoderImpl::MakeCurrent() 0x0000000108b31dae (Google Chrome Framework -gpu_command_buffer_stub.cc:504 ) gpu::GpuCommandBufferStub::OnMessageReceived(IPC::Message const&) 0x0000000108b2c74f (Google Chrome Framework -gpu_channel.cc:1037 ) gpu::GpuChannel::HandleMessageHelper(IPC::Message const&) 0x0000000108b25e40 (Google Chrome Framework -gpu_channel.cc:985 ) gpu::GpuChannel::HandleMessage(IPC::Message const&) 0x0000000108a2180a (Google Chrome Framework -callback.h:64 ) gpu::Scheduler::RunNextTask() 0x0000000107a3a27b (Google Chrome Framework -callback.h:64 ) base::debug::TaskAnnotator::RunTask(char const*, base::PendingTask*) 0x0000000107a5ef43 (Google Chrome Framework -message_loop.cc:394 ) base::MessageLoop::RunTask(base::PendingTask*) 0x0000000107a5f438 (Google Chrome Framework -message_loop.cc:406 ) base::MessageLoop::DoWork() 0x0000000107a612a9 (Google Chrome Framework -message_pump_mac.mm:452 ) base::MessagePumpCFRunLoopBase::RunWork() 0x0000000107a52439 (Google Chrome Framework + 0x01c53439 ) base::mac::CallWithEHFrame(void () block_pointer) 0x0000000107a60bce (Google Chrome Framework -message_pump_mac.mm:428 ) base::MessagePumpCFRunLoopBase::RunWorkSource(void*) 0x00007fff4466ca20 (CoreFoundation + 0x0009fa20 ) __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ 0x00007fff4472426b (CoreFoundation + 0x0015726b ) __CFRunLoopDoSource0 0x00007fff4464faaf (CoreFoundation + 0x00082aaf ) __CFRunLoopDoSources0 0x00007fff4464ef2c (CoreFoundation + 0x00081f2c ) __CFRunLoopRun 0x00007fff4464e786 (CoreFoundation + 0x00081786 ) CFRunLoopRunSpecific |
|||
►
Sign in to add a comment |
|||
Comment 1 by kbr@chromium.org
, Feb 8 2018Owner: kbr@chromium.org