My favorites | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 128415: Yet another crash in v8::internal::IncrementalMarking::Step
13 people starred this issue and may be notified of changes. Back to list
 
Project Member Reported by thestig@chromium.org, May 16, 2012
Product, Version	 Chrome_Linux ,  20.0.1132.3
ptype	 renderer

http://crash/reportdetail?reportid=066ae6dbb56bb0e1

Thread 0 *CRASHED* ( SIGSEGV @ 0x00000000 )

0x7f7784342980	 [chrome]	 - v8/src/objects-inl.h:529]	v8::internal::IncrementalMarking::Step
0x7f77842fba48	 [chrome]	 - v8/src/heap.cc:4973]	v8::internal::Heap::AdvanceIdleIncrementalMarking
0x7f77842fc492	 [chrome]	 - v8/src/heap.cc:5070]	v8::internal::Heap::IdleNotification
0x7f7785aaba59	 [chrome]	 - content/renderer/render_thread_impl.cc:641]	RenderThreadImpl::IdleHandler
0x7f7783f8370c	 [chrome]	 - ./base/callback.h:272]	base::Timer::RunScheduledTask
0x7f7783f5f8f8	 [chrome]	 - ./base/callback.h:272]	MessageLoop::RunTask
May 18, 2012
#1 kar...@google.com
(No comment was entered for this change.)
Status: Assigned
Owner: danno@chromium.org
May 21, 2012
#2 danno@chromium.org
(No comment was entered for this change.)
Owner: mstarzinger@chromium.org
May 30, 2012
#3 thestig@chromium.org
Seems to happen a lot to Googlers. This is the top Linux renderer crash in M20.

http://crash/reportdetail?reportid=14e86b0464710f08
http://crash/reportdetail?reportid=8d718e6f02f8be0e
http://crash/reportdetail?reportid=179f4c8ee01b1502
Labels: -Pri-2 Pri-1 Mstone-20
Jun 15, 2012
#4 dhar...@chromium.org
any updates?
Jun 15, 2012
#5 kar...@google.com
they are still happening a lot especially on the Mac. Any progress?

http://crash/reportdetail?reportid=8fc0ad78d456395b#crashing_thread
http://crash/reportdetail?reportid=d9435d2f539788e6#crashing_thread
http://crash/reportdetail?reportid=ebe996af1be38b62#crashing_thread
http://crash/reportdetail?reportid=5134a26d4269e3a3#crashing_thread
Jun 19, 2012
#6 mstarzinger@chromium.org
The frequency of this crasher has significantly dropped again on Canary releases (especially on Mac) since 21.0.1172.0 and is no longer a top crasher. The temporary spike in crashers might have been caused by an issue we fixed with the following revision.

https://code.google.com/p/v8/source/detail?r=11713

We'll continue to keep an eye on crashers with that stack signature. But at the current crash rate it's not a high priority issue.
Jul 11, 2012
#7 tony@chromium.org
http://b/6803828 looks like it might be related and it sounds like they have a repro. That bug has 12 crash IDs attached to it.
Jul 12, 2012
#8 mstarzinger@chromium.org
Thanks for the link. Having a repro would be awesome. I'll follow up.
Oct 19, 2012
#9 kar...@google.com
this is the top crash for linux on m23. is there nothing we can do?

http://crash/reportdetail?reportid=66c05612b9e68c15#crashing_thread
Oct 27, 2012
#10 dhar...@google.com
This is one of the top crashes in M24 Mac - 1305.3. Is there any fix that we could take?

https://crash.corp.google.com/reportdetail?reportid=2e781717762adcbf#crashing_thread
Mar 10, 2013
#11 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Area-WebKit -WebKit-JavaScript -Mstone-20 Cr-Content Cr-Content-JavaScript M-20
Apr 5, 2013
#12 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Cr-Content Cr-Blink
Apr 5, 2013
#13 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Cr-Content-JavaScript Cr-Blink-JavaScript
Jul 1, 2013
#14 ulan@chromium.org
 Issue 254182  has been merged into this issue.
Cc: shecky...@chromium.org mstarzinger@chromium.org hpa...@chromium.org
Sep 26, 2013
#15 vabr@chromium.org
Since today I started getting 100% reproducible crashes on loading particular docs in GDrive. The crash IDs I got are:
0e70d45a40f12642 --> pointing me to this bug by crashing signature
but also, e.g., f5c9230de2858618.

I'm seeing this on 30.0.1599.59 (Official Build 225043) beta on Linux, but it works fine in ToT Chromium debug build (32.0.1652.0 (Developer Build 225168)).
I have no issues on Mac and no issues on CrOS.
I tried running in a fresh profile, running in a fresh user data dir, and disabling extensions. None of that helped.
An interesting fact is that this seems to be tied to my @google.com account. When I open the crashing doc under my @chromium.org account, there is no issue.

If you think this is unrelated, let me know and I'll file a new bug.
I have enough workarounds (using other OS or the ToT build or other accounts), just wanted to offer a reproduction case if needed.
Sep 26, 2013
#16 vabr@chromium.org
As a follow-up to #15 -- I also tried this whithout signing-up, just with logging into drive with my @google.com account. The problem was still there, so it's not a profile corruption.
Mar 14, 2014
#17 rponn...@chromium.org
Same Crash happening on M35 latest canary: 35.0.1888.0 - go/crash/2804e6ff49c2b8ea




Cc: ligim...@chromium.org kar...@google.com
Mar 19, 2014
#18 mbo...@chromium.org
Issue 342655 has been merged into this issue.
Sign in to add a comment

Powered by Google Project Hosting