My favorites | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
  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, May 16, 2012
Product, Version	 Chrome_Linux ,  20.0.1132.3
ptype	 renderer


Thread 0 *CRASHED* ( SIGSEGV @ 0x00000000 )

0x7f7784342980	 [chrome]	 - v8/src/objects-inl.h:529]	v8::internal::IncrementalMarking::Step
0x7f77842fba48	 [chrome]	 - v8/src/]	v8::internal::Heap::AdvanceIdleIncrementalMarking
0x7f77842fc492	 [chrome]	 - v8/src/]	v8::internal::Heap::IdleNotification
0x7f7785aaba59	 [chrome]	 - content/renderer/]	RenderThreadImpl::IdleHandler
0x7f7783f8370c	 [chrome]	 - ./base/callback.h:272]	base::Timer::RunScheduledTask
0x7f7783f5f8f8	 [chrome]	 - ./base/callback.h:272]	MessageLoop::RunTask
May 18, 2012
(No comment was entered for this change.)
Status: Assigned
May 21, 2012
(No comment was entered for this change.)
May 30, 2012
Seems to happen a lot to Googlers. This is the top Linux renderer crash in M20.

Labels: -Pri-2 Pri-1 Mstone-20
Jun 15, 2012
any updates?
Jun 15, 2012
they are still happening a lot especially on the Mac. Any progress?

Jun 19, 2012
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.

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
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
Thanks for the link. Having a repro would be awesome. I'll follow up.
Oct 19, 2012
this is the top crash for linux on m23. is there nothing we can do?

Oct 27, 2012
This is one of the top crashes in M24 Mac - 1305.3. Is there any fix that we could take?
Mar 10, 2013
(No comment was entered for this change.)
Labels: -Area-WebKit -WebKit-JavaScript -Mstone-20 Cr-Content Cr-Content-JavaScript M-20
Apr 5, 2013
(No comment was entered for this change.)
Labels: -Cr-Content Cr-Blink
Apr 5, 2013
(No comment was entered for this change.)
Labels: -Cr-Content-JavaScript Cr-Blink-JavaScript
Jul 1, 2013
 Issue 254182  has been merged into this issue.
Sep 26, 2013
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 account. When I open the crashing doc under my 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
As a follow-up to #15 -- I also tried this whithout signing-up, just with logging into drive with my account. The problem was still there, so it's not a profile corruption.
Mar 14, 2014
Same Crash happening on M35 latest canary: 35.0.1888.0 - go/crash/2804e6ff49c2b8ea

Mar 19, 2014
Issue 342655 has been merged into this issue.
Sign in to add a comment

Powered by Google Project Hosting