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

Issue 738793 link

Starred by 5 users

Issue metadata

Status: Fixed
Owner:
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Chrome crashes is observed while pasting long data in Google sheet.

Reported by dchau...@etouch.net, Jul 3 2017

Issue description

Chrome Version: 61.0.3147.0 (Official Build) e6db2be32f63ad9c3b8bce1b4f0dab810a7f2622-refs/heads/master@{#483897} 32/64-bit.
OS: Windows (7,8,10), Linux.

What steps will reproduce the problem?
1. Launch chrome and login to www.drive.google.com with valid credentials.
2. Create a google sheet (Ex: sheet 1) with large data and copy whole data.
3. Now, crate a new Google sheet (Ex: sheet 2) in the same drive and paste the copied data from sheet 1 into sheet 2.
4. Observe.

chrome crashes while pasting data.
Chrome should not crash.

Crash ids: 89664ade40000000 (Local Crash ID: 989282d5-e3a1-4622-9709-dcd1def50423)

This is a regression issue, broken in M-61 series, will soon update other info.
 
Labels: OS-Mac
Manual regression range:

Good build: 61.0.3144.0 
Bad build: 61.0.3145.0

Note: This issue is also reproducible on Mac OS.

Kindly review the attached screen-cast for reference.
Actual behavior.mp4
3.9 MB View Download
Expected behavior.mp4
2.9 MB View Download
Cc: -rbasavalu@chromium.org rbasuvula@chromium.org
Labels: hasbisect-per-revision ReleaseBlock-Beta
Owner: machenb...@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build:61.0.3144.0(Revision:483234).
Bad build:61.0.3145.0(Revision:483574).

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

CHANGE-LOG URL:
---------------
https://chromium.googlesource.com/chromium/src/+log/d1ba25881cbb45cc23a1f446ac174842986161c0..6ae8ca822914c7216962dbf2255af34aa5605622
In V8 - AutoRoll
https://chromium.googlesource.com/v8/v8/+log/8ff4cb25..69a568f8

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

@machenbach: 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/2962163002
Note :Able to reproduce the issue in Win 10.0,Ubuntu 14.04 & Mac 10.12.5 and Able to reproduce in latest Canary #61.0.3147.0
Adding Release Block-Beta for this issue.Please remove if not the case.

Stack Trace:
------------
Thread 16 (id: 3612) CRASHED [EXCEPTION_ACCESS_VIOLATION_READ @ 0x00000000 ] MAGIC SIGNATURE THREAD
Stack Quality100%Show frame trust levels
0x000007fee4b7fb60	(chrome_child.dll -scheduler.cc:1625 )	v8::internal::compiler::ScheduleLateNodeVisitor::ScheduleRegion(v8::internal::compiler::BasicBlock *,v8::internal::compiler::Node *)
0x000007fee4860610	(chrome_child.dll -scheduler.cc:1421 )	v8::internal::compiler::ScheduleLateNodeVisitor::VisitNode(v8::internal::compiler::Node *)
0x000007fee4860481	(chrome_child.dll -scheduler.cc:1369 )	v8::internal::compiler::ScheduleLateNodeVisitor::ProcessQueue(v8::internal::compiler::Node *)
0x000007fee48052d0	(chrome_child.dll -scheduler.cc:1678 )	v8::internal::compiler::Scheduler::ScheduleLate()
0x000007fee4805491	(chrome_child.dll -scheduler.cc:61 )	v8::internal::compiler::Scheduler::ComputeSchedule(v8::internal::Zone *,v8::internal::compiler::Graph *,v8::base::Flags<v8::internal::compiler::Scheduler::Flag,int>)
0x000007fee47fe116	(chrome_child.dll -pipeline.cc:1203 )	v8::internal::compiler::EffectControlLinearizationPhase::Run(v8::internal::compiler::PipelineData *,v8::internal::Zone *)
0x000007fee47fe089	(chrome_child.dll -pipeline.cc:817 )	v8::internal::compiler::PipelineImpl::Run<v8::internal::compiler::EffectControlLinearizationPhase>()
0x000007fee47ff540	(chrome_child.dll -pipeline.cc:1744 )	v8::internal::compiler::PipelineImpl::OptimizeGraph(v8::internal::compiler::Linkage *)
0x000007fee47fe40e	(chrome_child.dll -pipeline.cc:652 )	v8::internal::compiler::PipelineCompilationJob::ExecuteJobImpl()
0x000007fee4695396	(chrome_child.dll -compiler.cc:134 )	v8::internal::CompilationJob::ExecuteJob()
0x000007fee47fd21a	(chrome_child.dll -optimizing-compile-dispatcher.cc:115 )	v8::internal::OptimizingCompileDispatcher::CompileNext(v8::internal::CompilationJob *)
0x000007fee47fd171	(chrome_child.dll -optimizing-compile-dispatcher.cc:67 )	v8::internal::OptimizingCompileDispatcher::CompileTask::Run()
0x000007fee4682a86	(chrome_child.dll -callback.h:91 )	base::Callback<void ,0,0>::Run( ?? )
0x000007fee46829ff	(chrome_child.dll -task_annotator.cc:59 )	base::debug::TaskAnnotator::RunTask(char const *,base::PendingTask *)
0x000007fee468366f	(chrome_child.dll -task_tracker.cc:335 )	base::internal::TaskTracker::PerformRunTask(std::unique_ptr<base::internal::Task,std::default_delete<base::internal::Task> >,base::internal::Sequence *)
0x000007fee468509b	(chrome_child.dll -task_tracker.cc:251 )	base::internal::TaskTracker::RunNextTask(base::internal::Sequence *)
0x000007fee46833d3	(chrome_child.dll -scheduler_worker.cc:80 )	base::internal::SchedulerWorker::Thread::ThreadMain()
0x000007fee480d93b	(chrome_child.dll -platform_thread_win.cc:89 )	base::`anonymous namespace'::ThreadFunc
0x76a959cc	(kernel32.dll + 0x000159cc )	BaseThreadInitThunk
0x76f4b980	(ntdll.dll + 0x0002b980 )	RtlUserThreadStart

Thank You!
Components: Blink>JavaScript>Compiler
Owner: ----
Status: Untriaged (was: Assigned)
-> V8 compiler triage queue.
Cc: bmeu...@chromium.org jarin@chromium.org
Owner: tebbi@chromium.org
Status: Assigned (was: Untriaged)
Project Member

Comment 5 by sheriffbot@chromium.org, Jul 3 2017

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

Win Canary 61.0.3147.0 -  2.11 CPM, 42 reports, 35 clients (signature v8::internal::compiler::ScheduleLateNodeVisitor::ScheduleRegion)

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

- Go/Fracas

Comment 6 by tebbi@chromium.org, Jul 5 2017

Issue 738781 has been merged into this issue.

Comment 7 by tebbi@chromium.org, Jul 5 2017

Status: Fixed (was: Assigned)
The triggering change has been reverted already (https://codereview.chromium.org/2970663002/), but the root cause still has to be addressed.

Sign in to add a comment