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

Issue 854843 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Nov 24
Cc:
Components:
EstimatedDays: ----
NextAction: 2018-07-31
OS: Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Mac renderer crash rate has spiked on 67.0.3396.87 when compared to 66.0.3359.181.

Project Member Reported by pbomm...@chromium.org, Jun 20 2018

Issue description

UMA data : https://uma.googleplex.com/timeline_v2?sid=b595c06b010fcc667d355d0506de4310 


Magic signatures which have caused this spike based on renderer crash comparison from 66.0.3359.181 to 67.0.3396.87.

840446(Spiked by ~3.0%) : Offscreen::getCG [As per the latest update this is deep in CoreGraphics and hard to pin point from SKIA team] 
820218(Spiked by 0.94%) : v8::internal::ConcurrentMarkingVisitor::ProcessStrongHeapObject [ Wontfix]
841167(Spikes by 0.72%) : blink::PaintLayerPainter::PaintFragmentWithPhase [Got punted to M68]
846227(Spiked by 0.44%) : blink::PaintLayerPainter::AdjustForPaintProperties[Got punted to M68]
853236(Spiked by 0.44%) : blink::MarkingVisitor::Visit
847751(Spiked by 0.49%) : v8::internal::LocalEmbedderHeapTracer::RegisterWrappersWithRemoteTracer [crashes are seen only on M67 stable still been investigated]
846227(Spiked by 0.44%) : blink::PaintLayerPainter::AdjustForPaintProperties [Punted to M68]
 
Components: Blink>Paint
Cc: chrishtr@chromium.org pdr@chromium.org
Labels: Needs-Feedback
NextAction: 2018-07-09
Really ticked up from 67.0.3396.62 to 67.0.3396.79 according to that uma link.

This is the change log.
https://chromium.googlesource.com/chromium/src/+log/67.0.3396.62..67.0.3396.79?pretty=fuller&n=10000

Of the changes here, the only ones related to paint that would cause a tick up in crashes are the foreign object fixes. Maybe that points to the source of the problems.

pbommana@, what is the goal with this bug? It seems that all the contributing failures are covered by other bugs.
This bug is logged to track stable crash rates spikes to present during the stability meeting. 

Abdul please add more if I am wrong.
The NextAction date has arrived: 2018-07-09
NextAction: 2018-07-31
The NextAction date has arrived: 2018-07-31
Owner: pbomm...@chromium.org
Status: Assigned (was: Untriaged)
Can this be closed now that M-68 is shipped to stable and M-67 is being retired?
What's the status on this. Can we close it?
Status: WontFix (was: Assigned)

Sign in to add a comment